2024 Technology Preview Program:
Master powerful new features and shape the latest BIM-enabled innovations
2006-06-21
05:04 PM
- last edited on
2023-08-07
11:12 AM
by
Doreena Deng
2006-06-21 08:49 PM
Dipan wrote:I assume you mean .NET WinForms? I can't comment on whether this should work or not, but I definitely recommend using the UI mechanisms provided by the ArchiCAD API. Otherwise you may find yourself having to do a lot of extra work integrating your UI with ArchiCAD (especially emulating special controls for attributes like pens etc).
Hi,
I have just started learning how to create ArchiCAD addons using VC++ .NET. When I create a new ArchiCAD addon project and compile it it works fine. However when I try to add a new windows form, it fails to compile.
Dipan
2006-06-21 09:17 PM
2006-06-21 09:28 PM
2006-06-21 09:59 PM
Dipan wrote:Take a look at the documentation for the 'DialogManager'. This comrpehensively covers the dialog and control types available through the API. Alos, make sure you look at the GRC documentation, e.g. "GRC Specification of the Dialog Types". This is Graphisoft's primary mechanism for describing cross-platform resources.
Can you suggest how to work with the ArchiCAD API UIs?? Just tell me where and how to start.
2006-06-22 12:53 AM
2006-07-03 06:26 PM
Dipan wrote:
ACAP_STAT.lib(ACAPlib.obj) : warning LNK4099: PDB 'api_c.pdb' was not found with '\Program Files\Graphisoft\API Development Kit 10.20\Support\Lib\Win\ACAP_STAT.lib' or at 'c:\Program Files\Graphisoft\API Development Kit 10.20\Examples\DG_Test\Debug\api_c.pdb'; linking object as if no debug info
Dipan wrote:
The compiling was succesful but was incorrect as the Addon admin did not recognise it as a valid addon.
2006-07-04 05:08 PM
"Andras Babos" wrote:"Dipan Das" wrote:
ACAP_STAT.lib(ACAPlib.obj) : warning LNK4099: PDB 'api_c.pdb' was not found with '\Program Files\Graphisoft\API Development Kit 10.20\Support\Lib\Win\ACAP_STAT.lib' or at 'c:\Program Files\Graphisoft\API Development Kit 10.20\Examples\DG_Test\Debug\api_c.pdb'; linking object as if no debug info
That's all right. No need to worry about that warning, as it complains about a debug info file which is deliberately not supplied with the API DevKit. You don't need it anyway.
"Dipan Das" wrote:
The compiling was succesful but was incorrect as the Addon admin did not recognise it as a valid addon.
That's because you didn't supply a valid Developer ID and Add-On ID in the GRC files. (Please see the 'Required Resources' page in the API documentation.)