BIM Coordinator Program (INT) April 22, 2024

Find the next step in your career as a Graphisoft Certified BIM Coordinator!

Libraries & objects
About Archicad and BIMcloud libraries, their management and migration, objects and other library parts, etc.
SOLVED!

Working of COOR{3}

runxel
Legend
Why does always just the last COOR{3} statement take effect?
How can I cancel that behaviour?
CPRISM_ ...
COOR{3} ...

! Later:
CPRISM_ ...
COOR{3} ...
In this shortened example the first COOR{3} doesn't seem to take place at all / gets overridden by the second one.
Lucas Becker | AC 27 on Mac | Author of Runxel's Archicad Wiki | Editor at SelfGDL | Developer of the GDL plugin for Sublime Text |
«Furthermore, I consider that Carth... yearly releases must be destroyed»
1 ACCEPTED SOLUTION

Accepted Solutions
Solution
Barry Kelly
Moderator
Isn't that when you need to use the BODY 1 after the COOR?
I may be wrong - I haven't tested it.

i.e.
CPRISM_ ... 
COOR{3} ... 
BODY 1

! Later: 
CPRISM_ ... 
COOR{3} ...
BODY 1
Barry.
One of the forum moderators.
Versions 6.5 to 27
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Lenovo Thinkpad - i7-1270P 2.20 GHz, 32GB RAM, Nvidia T550, Windows 11

View solution in original post

5 REPLIES 5
Solution
Barry Kelly
Moderator
Isn't that when you need to use the BODY 1 after the COOR?
I may be wrong - I haven't tested it.

i.e.
CPRISM_ ... 
COOR{3} ... 
BODY 1

! Later: 
CPRISM_ ... 
COOR{3} ...
BODY 1
Barry.
One of the forum moderators.
Versions 6.5 to 27
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Lenovo Thinkpad - i7-1270P 2.20 GHz, 32GB RAM, Nvidia T550, Windows 11
runxel
Legend
Barry wrote:
Isn't that when you need to use the BODY 1 after the COOR?
Wow, thanks Barry.
I saw it – and didn't even bother trying, because it's clearly stated, that "BODY 1" is deprecated...

But! – it works. So I'm gonna keep it. Thanks again!
Lucas Becker | AC 27 on Mac | Author of Runxel's Archicad Wiki | Editor at SelfGDL | Developer of the GDL plugin for Sublime Text |
«Furthermore, I consider that Carth... yearly releases must be destroyed»
Barry Kelly
Moderator
I think it means that COOR{1} and COOR{2} are deprecated and replaced with COOR{3}
There is no need to define the VERTs now and it is not very clear but I think the BODY 1 is still needed to define the end of the form (body) that the COOR works on.

Barry.
One of the forum moderators.
Versions 6.5 to 27
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Lenovo Thinkpad - i7-1270P 2.20 GHz, 32GB RAM, Nvidia T550, Windows 11
runxel
Legend
Barry wrote:
I think it means that COOR{1} and COOR{2} are deprecated and replaced with COOR{3}
Yes, but have a look for yourself here.
It clearly states
j1: closed body (deprecated)
And it is not really verbose in everything else; that the BODY 1 is needed is never stated anywhere.
So thanks again for pointing me to the right direction
Lucas Becker | AC 27 on Mac | Author of Runxel's Archicad Wiki | Editor at SelfGDL | Developer of the GDL plugin for Sublime Text |
«Furthermore, I consider that Carth... yearly releases must be destroyed»
Barry Kelly
Moderator
runxel wrote:
Yes, but have a look for yourself here.
It clearly states
j1: closed body (deprecated)
Ah that is the 'status' in the BODY command.
j1 & j2 are deprecated.
The BODY command itself still works.

Just not clear in the examples of COOR, COOR{2} & COOR{3} that you still need to use BODY.

Actually when I first answered you I was looking in an old GDL book - version 6.5 that only has COOR.
This is the last physical GDL manual and I still have it sitting on my desk as I find it easier than the PDFs when I want to find something quickly.
I just assumed it would be the same for COOR{2} and COOR{3} - lucky guess maybe?

Barry.
One of the forum moderators.
Versions 6.5 to 27
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Lenovo Thinkpad - i7-1270P 2.20 GHz, 32GB RAM, Nvidia T550, Windows 11
Learn and get certified!