Dimensioning windows

[GFBArchitect]

Sometimes when I dimension windows to the center line, it seems to do it just fine but later, when I've plotted the drawing, I see that ArchiCad has changed it to show the dimension to one edge of the window instead. What causes this?

[Erika Epstein]

Am I correct in understanding that it shows in AC one way but prints differently?

[GFBArchitect]

The program changes the dimension on the drawing. I'm not sure if it happens after printing or after closing / opening program.

[Arcadia]

I would change your dimensioning method to dimension the width of the window not the center. I would have thought this was a more useful dimension for the builder than a centre dimension? Not sure why this would happen - what library are the windows from? I have a 3D library object from a third party library that consistently does weird things with dimensions so maybe it is a code issue with the windows?

[GFBArchitect]

Builders specifically want the windows dimensioned to the centerline as they may bid several windows with slightly different r.o.'s Thanks for the reply.

[Anonymous]

Sounds a lot like the 'jumping dimensions' game that happens here!!!
It is something to do with the hotspots in the object it's self!
We have it happen here a heap on one object in particular and I have been told it has something to do with the GDL hotspot's ID and when ArchiCAD rebuilds.
It's annoying to say the least!!!!
We get around it by dimensioning a hotspot and then dragging said hotspot into position!!
In saying that I seriously do not recommend that method!!!

[Barry Kelly]

When you dimension a hotspot that is scripted into an object and that hotspot has an ID number then that dimension will lock to that hotspot and move when ever the hotspot moves.

If the hotspot does not have an ID then the dimension will not adjust.

The problem with hotspot ID's occurs if your object has automatically numbering ID's (i.e "HSID = HSID + 1" in the scripts).
Then if a hotspot is not used or a new one is (within IF / THEN statements)
or you call another macro with hotspaots with ID's then all of the ID numbers will get mixed up and the dimension will try to link to the hotspot that had the original ID number.
This could be a completely different hotspot now or it may no longer exist at all.
Which is why dimension jump around or disappear.

The best solution is to hard code all of the ID numbers which means individually numbering all of the hotspots in a script manually.
Still doesn't help when you call in a macro but this is not usally a big problem and can be worked around.

Barry.

[Anonymous]

Barry

I've actually tried all that mate! For some reson it just wont stick!!
I must admit it happens less now but it still pops up every now and then!

[Barry Kelly]

Hi Kristian,
It can be very frustrating.
Converting an existing object to have static ID's isn't always easy as you have to follow the order the hotspots are created in and IF/THEN and GOSUBS complicate the matter considerably.
If you do convert to static ID's you can only assume (hope!) that objects dimensioned in the future will behave correctly and that already dimensioned objects may still mess up.
Barry.

[Anonymous]

Ahhhh That is one thing I havent actually tried, going thru in the actual read order not the script order!!!
I'm actually going to have to give that a crack!! Thanks for the heads up on that one mate!!