2021-12-13 06:34 PM
I do a fair bit of GDL work, and I have been personally frustrated over the last few versions of Archicad that the GDL environment has become much more crashy, and of course there is no autosave, which inevitably results in lost work, often hard work, because GDL is a miserable language in the first place.
When I have complained about this in the past, I am duly patted on the head and reminded that GDL users are an absolutely insignificant minority of AC users, and there is simply no chance of any development or QA resources being spent in this area.
It has taken me a while, I’m embarrassed to admit, but I have belatedly gained wisdom about this situation. Now whenever the GDL environment crashes, I rejoice that no resources have been spent on it, and with the resulting ample attention available, the rest of Archicad should be perfect real real soon.
2021-12-13 11:31 PM
If I didn't know better I might assume this was written with a hint of sarcasm 🤔
2021-12-14 12:40 AM
if its not sarcasm i completely disagree..
the only time something crashes is when i code an unending loop unintentionally lol
otherwise how can you really complain about basic math lol
2021-12-14 03:04 PM
I actually have no complains nor problems with GDL, but have exactly that same opinión about how GS made lists system die, no schem solution can have EVER the level of detail I had with bills of materials generated with list
2021-12-20 07:08 AM - edited 2021-12-20 07:09 AM
On Mac since some Versions, its very well known, that the action "mouse-draw of code-passages" causes the gdl-editor to display false code. If you do so, you have to save your work with knowing of the false code, because you cant see it. Then, after re-opening, You can see the wrong passages of the code and correct it. So - on Mac, the only way of changing code-Place is "keyboard-copy-paste". With the Mouse, You get in trouble.
As i said - this Bug is very well known by Graphisoft since some Versions and was never corrected.
2021-12-20 12:28 PM
Yes, that is true, but at least GDL, with glitches, is still working
2022-01-13 02:21 AM - edited 2022-01-13 03:12 PM
At least it would be super handy to know how the heck, using what workflow, what debugging tools, what macros managing system is Graphisoft's in-house GDL library developer team making his daily work. This would be super handy, to say the least. As it is a know-how of one (quite an important part) of a comercial tool we are paying for, it makes sense to have a good reference to look into. Does it exist? I ignore...
2022-01-13 10:01 AM
That's a very good question. It's hard to believe that the library developers are using the native AC GDL scripting interface after all these years? It should have a much more efficient interface by now if they are using it.
2022-01-13 12:18 PM
for your interest, I have created a wish for a webinar (?) on this topic
2022-01-13 12:26 PM
I have recently started using VScode for my GDL development process, editing them in xml format paired with a batch script for automating the xml to gsm conversion, and I must say I feeling quite comfortable with the new workflow.
"testing" the GDL codes takes some extra steps, save xml,convert to gsm, update Archicad library, but it is less than 10 seconds. In Archicad 25 now its also possible to automate the library updating process with python (i'm not currently working in a AC 25 project though but i'll implement that on future projects, for sure)