Not signed in (Sign In)

Vanilla 1.1.4 is a product of Lussumo. More Information: Documentation, Community Support.

Welcome Guest!
Want to take part in these discussions? If you have an account, sign in now.
If you don't have an account, apply for one now.
    • CommentAuthorryobg
    • CommentTimeOct 28th 2017 edited
     
    Hello again,

    I was trying to post few times at the Yahoo Dev list, but at the best my shortest dummy message arrived after 4 hours. So full of that, I come here.

    I want to excuse myself to everybody for this highly technical question, but I hope it can be seen from some of the SW developers.
    It basically continues https://groups.yahoo.com/neo/groups/CC2-DEV-L/conversations/messages/973

    So...

    1) [OPTIONAL] I would like to tag with some plain data the Symbol Definitions. This would be done once per symbol of interest, done once or rarely updated.
    If I can script somewhat this would be great. Imagine that there will be way to: "Aaahh... same symbol I see now, so here it is his key=value pairs"
    This data associated should be persistent of course. And can be even one field of data only.

    2) During CC3+ session, an user should be able to associate to each instance of symbol again some tag(s).

    3) Later, best if it is only the file itself, the map will be parsed by external tool and data be extracted.
    Data includes the common symbol info like position, extent, sheet, etc.. But also the Symbol Def and Symbol Instance custom fields.

    I think I can describe as this the best scenario.
    I'm experienced in C/C++, SDK, API, Libraries and etc. IF there is a good documentation of course.

    With best regards.
    • CommentAuthorjslayton
    • CommentTimeNov 7th 2017
     
    From your description, it sounds like you would be best served by writing an XP (FastCAD plugin DLLs) that allows you to keep your information directly in the file. The XP would provide a dialog that lets the user edit the information and associate information with entities. For simplicity, you could keep the database stored in the form of map notes (text strings). I recommend map notes because that way you would not need to have your custom XP handy to look at or edit tags and I think that there's a way to export map notes to a file. Your XP could, of course, provide an export format that exactly meets your needs. Each entity has a tag ID associated with it and you can use that tag ID as a key to associate notes with entities.

    There is a CC3 developer kit running around somewhere that describes writing XPs and there is also a set of tutorials for doing so. I'm not sure what the status is for the CC3+ developer kit, though, but it shouldn't be hugely different for the basic elements. CC3+ is using Visual Studio 2013 as its build environment at the moment, but the general FastCAD interface is simple DLLs with a C API for most interaction.
    • CommentAuthorryobg
    • CommentTimeNov 10th 2017 edited
     
    Hi! I much appreciate your feedback - thank you!

    from this topic: http://forum.profantasy.com/comments.php?DiscussionID=62
    I have found this SDK: http://www.pkdata.se/xp/download/xpdev-cc3.zip
    And I also found tutorials at: https://cc3-developer.blogspot.bg/

    I'm bit concerned as these are:
    1. For CC3 not CC3+
    2. The blog posts are 3-4 years old
    3. The SDK is like 12 years old

    Do you think that is fine?
    •  
      CommentAuthorMonsen
    • CommentTimeNov 10th 2017
     
    They should work fine. The file and entity format haven't changed between CC3 and CC3+. You may need newer files to access new functionality added to CC3+, but it doesn't sound like that is something you will be needing for your project, you seem to be more interested in the basic entity information.
    • CommentAuthorryobg
    • CommentTimeNov 10th 2017
     
    Thank you Monsen too. The ball is on my side now.
    •  
      CommentAuthorMonsen
    • CommentTimeNov 10th 2017
     
    Good luck, and don't be afraid to ask more questions. My own knowledge when it cones to XP's aren't all that complete, but Joe is usually full of good answers.
    And remember to read the included header files, they often provide lots of information not mentioned in the documentation.