Oops there is a bug 😉 in my attached 2nd screenshot. 
The ID's must be shown all the same!
That's was the purport!
The ID's must be shown all the same!
That's was the purport!
Hello Barry,
Hallo Frank,
I have another version of "external counter".
So what's difference between mine's and Frank's?
Frank your script in general is well wrote, but in some cases AC9 hangs/crashes. I had not enough time to understand the problem!
In my script if .txt file is not founded, then DIALOG appears where locate it. If you havn't created .txt file yet, then create new one (for example: "ProjectName+DBT_NCS Counter.txt") and open.
With mine's you have possibility to start from that point that you wish, but for do that you must open *.txt file and edit it. It's not very agreeable, but at the moment I have no idea how others it can be done using GDL.
I send you tomorrow "ReadMe.txt" file to explain how external file can/must be edited.
I wrote in AC9
I havn't added limitation, but maybe will add as uncommented script.
P.S.: The counting script is already integrated in to "Drawing Block Title_NCS.gsm"
Hallo Frank,
I have another version of "external counter".
So what's difference between mine's and Frank's?
Frank your script in general is well wrote, but in some cases AC9 hangs/crashes. I had not enough time to understand the problem!
"F. Beister" wrote:
...object generates a new textfile each time you change the filename. Without a path it will be saved in archicad projet folder (or DATA-folder there).
In my script if .txt file is not founded, then DIALOG appears where locate it. If you havn't created .txt file yet, then create new one (for example: "ProjectName+DBT_NCS Counter.txt") and open.
"F. Beister" wrote:
With mine's you have possibility to start from that point that you wish, but for do that you must open *.txt file and edit it. It's not very agreeable, but at the moment I have no idea how others it can be done using GDL.
I send you tomorrow "ReadMe.txt" file to explain how external file can/must be edited.
"F. Beister" wrote:
I wrote in AC9
"F. Beister" wrote:
I havn't added limitation, but maybe will add as uncommented script.
P.S.: The counting script is already integrated in to "Drawing Block Title_NCS.gsm"
Maybe I misunderstood your solution and I have to admit, that I don't have analyzed the "Drawing Block Title-NCS".
My conclusion was that there are two ways to increase a counting number by placing an object:
1. To use the global ID, which can to be used as an increasing numbering. This is built in and can be used with all elements, which can have an ID.
2. To script an increasing counter inside the GDL. This was asked for a few times here and in other talks. This is, as I mentioned before not so easy, because the several occurances of objects inside a project can't communicate in between to return the last, highest counter. For this you have to make the trick to do it outside the script and plan in a separate file.
Why to use solution 2 instead of 1? Because some users use the GLOB_ID as an Identifier for elements. E.g. "App.01" to group several elements (mixed walls, objets etc.) together. In this case the misusage of the GLOB_ID is a limitation of the normal workflow.
My object is a feasibility study. One can add a deleting of numbers, reset to a current value etc. as counting without limitation to it as you like without editing the txt-file. You know: It's GDL, all is possible.😉
Easiest way is (1), counting by the auto increasing Identifier. But in the moment you want to increase letters (A,B,C...), or other steps (01,03,05...) or directions (10,9,8,...) you will have to make it this way. Wheras one could do this in GDL by using the GLOB_ID too.
My conclusion was that there are two ways to increase a counting number by placing an object:
1. To use the global ID, which can to be used as an increasing numbering. This is built in and can be used with all elements, which can have an ID.
2. To script an increasing counter inside the GDL. This was asked for a few times here and in other talks. This is, as I mentioned before not so easy, because the several occurances of objects inside a project can't communicate in between to return the last, highest counter. For this you have to make the trick to do it outside the script and plan in a separate file.
Why to use solution 2 instead of 1? Because some users use the GLOB_ID as an Identifier for elements. E.g. "App.01" to group several elements (mixed walls, objets etc.) together. In this case the misusage of the GLOB_ID is a limitation of the normal workflow.
My object is a feasibility study. One can add a deleting of numbers, reset to a current value etc. as counting without limitation to it as you like without editing the txt-file. You know: It's GDL, all is possible.
Easiest way is (1), counting by the auto increasing Identifier. But in the moment you want to increase letters (A,B,C...), or other steps (01,03,05...) or directions (10,9,8,...) you will have to make it this way. Wheras one could do this in GDL by using the GLOB_ID too.
I should have used the search button. For shure, Oleg gave us an example yet. I will have a look on it. Thanks for the hint.
I will have a look on it. Thanks for the hint.
Didn't find the answer?
Check other topics in this Forum
Back to ForumRead the latest accepted solutions!
Accepted SolutionsStart a new conversation!
