2009-06-01 12:42 PM
2009-06-05 09:28 PM
2009-06-05 11:31 PM
Braza wrote:That REQUEST is for GDL add-ons, not API add-ons, and so cannot interact with things such as Attribute Manager. It simply gives you an alternate syntax for calling GDL add-ons, such as the Text I/O add-on. Unless GS has changed something in recent years.
If I got it right... We can use an extension name as a request and extract information stored inside it...
2009-06-05 11:34 PM
2009-06-08 11:02 AM
Karl wrote:And how can I distinguish a GDL add-on from an API one?
That REQUEST is for GDL add-ons, not API add-ons
Karl wrote:So... its like a "remote control" for add-ons inside GDL script?...
It simply gives you an alternate syntax for calling GDL add-ons, such as the Text I/O add-on.
2009-06-08 06:20 PM
Braza wrote:See attached screenshot that lists the ones delivered with ArchiCAD 12.
And how can I distinguish a GDL add-on from an API one?
About ODBC... as SQL... it doesn't give a dynamic link with AC composites... and in my project this is essential.Well, yes and no on being dynamic. The link to the project file is 'live'. But, the query has to be refreshed in Access to see any changes.
Can you tell me whats the level of difficulty of scripting a GDL add-on which can provide this attribute information from a GDL object using this special REQUEST form?You need to be a reasonably advanced C/C++ programmer. I have not looked at the GDL developer kit in a few years, so don't know for sure if the composite information is even available to a GDL add-on. My memory is that it probably is not, as I seem to recall that GDL add-ons have access only to the GDL environment, not the project environment. So, you might have to write an API add-on that creates the desired GDL object (or populates its data) dynamically.
2009-06-08 07:03 PM
Karl wrote:You are right...
You haven't really saidwhyyou want a GDL object to list the entire list of composite attributes ...
2009-06-08 10:32 PM