Add-Ons Entry Point
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2023-06-02 06:16 AM
I am query how to set an entry point of addon.
Is there someone could provide detail of how to set/change an add on entry point file when running addon in Visual Studio C++?
- Labels:
-
Add-On (C++)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2023-06-02 09:07 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2023-06-02 02:57 PM
An information from that link, does it has to be 'Addonmain.cpp' as default entry point?. Could it be something like 'MyAddon.cpp' for entry point?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2023-06-02 03:13 PM
The entry points are explained in the 'anatomy of an addon' paragraph in the link I posted.
An archicad addon doesn't require a Main.cpp to work it can be named whatever you want.
The way you interact with archicad is either through menus or dialogs, palettes.
menus are defined in .grc file
dialogs or palettes are defined in cpp files.
You link the menu to your functions through MenuCommandHandler.
Look at the blog articles, there is a hello world example that explains all this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2023-06-02 03:46 PM
Thanks so much for your clarification. Besides this, the resource of .grc file explanation is very rare. For example, if I want to display a value getting from API function on the dialogs. Do I need to declare a text or label in .grc file or not? if so, how to implement this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2023-06-02 05:01 PM
Yes, every field in a dialog has to be declared in the grc file.
Look at DG_Test example in the API files.
Some articles explain this in the documentation.