topic Re: What determines zone belonging? in Modeling

What determines zone belonging?

Mats_Knutsson — Thu, 25 May 2023 15:53:52 GMT

Hi,

The attach is from a hospital project where we have to model the handle bars separately. We place them in the door opening which happens to be between two zones. When I schedule zone belonging for the objects the handle has none... When I move the handle into the zone I can't figure out when ArchiCAD decides it belongs to the zone. Anyone knows?

I there a way to force objects to belong to a zone even if they are not in the zone?

Best regards,
Mats

Re: What determines zone belonging?

Barry Kelly — Fri, 09 Nov 2018 01:57:15 GMT

It would be the default origin of the object.
What ever zone that origin is in will be the reported zone.

If you can edit the object you can trick it by adding a moveable hotspot that offsets your rail from that origin.
i.e. offsets the rail away from the door/wall - assuming the origin in on a point that fixes to the door/wall.

The problem is this will just move your rail away from the door/wall.
However you can add a value of 256 to the type 1 hotspot.
This will make the moving node stretchy on 2 directions.
One node will drag the rail away from the door (the origin), but the other will move the origin.
And because you are increasing the distance from the origin, the object will effectively stay in the same place.

This is a hotspot I use in an object that displays the name of the zone (see image).
I have used 'text_off' as the distance variable (parameter) but change it to what ever you want.

	unID=unID+1
	HOTSPOT2 0, 0, unID, text_off  1+256
	unID=unID+1
	HOTSPOT2 0, -0.0001, unID, text_off, 3
	unID=unID+1
	HOTSPOT2 0, text_off, unID, text_off, 2

Give an initial value for 'text_off' (say 200mm) so you can see the 2 hotspots.
It gets awkward if the value is zero as both hotspots will be on top of each other, and you have to move one out of the way to get to the one you want.

Use ADD2 text_off, 0 (or ADD2 0, text_off depending on the default rotation of your object) to move your object away from the origin.
When placing the object just don't use the origin hotspot, use one at the end of the rail to lock in on the door.
Now just stretch the hotspot into the zone you want.

Sorry if this doesn't make much sense.

Barry.

Re: What determines zone belonging?

Mats_Knutsson — Fri, 09 Nov 2018 07:41:04 GMT

Barry wrote:
It would be the default origin of the object.
What ever zone that origin is in will be the reported zone.

If you can edit the object you can trick it by adding a moveable hotspot that offsets your rail from that origin.
i.e. offsets the rail away from the door/wall - assuming the origin in on a point that fixes to the door/wall.

The problem is this will just move your rail away from the door/wall.
However you can add a value of 256 to the type 1 hotspot.
This will make the moving node stretchy on 2 directions.
One node will drag the rail away from the door (the origin), but the other will move the origin.
And because you are increasing the distance from the origin, the object will effectively stay in the same place.

This is a hotspot I use in an object that displays the name of the zone (see image).
I have used 'text_off' as the distance variable (parameter) but change it to what ever you want.
	unID=unID+1
	HOTSPOT2 0, 0, unID, text_off  1+256
	unID=unID+1
	HOTSPOT2 0, -0.0001, unID, text_off, 3
	unID=unID+1
	HOTSPOT2 0, text_off, unID, text_off, 2
Give an initial value for 'text_off' (say 200mm) so you can see the 2 hotspots.
It gets awkward if the value is zero as both hotspots will be on top of each other, and you have to move one out of the way to get to the one you want.

Use ADD2 text_off, 0 (or ADD2 0, text_off depending on the default rotation of your object) to move your object away from the origin.
When placing the object just don't use the origin hotspot, use one at the end of the rail to lock in on the door.
Now just stretch the hotspot into the zone you want.

Sorry if this doesn't make much sense.

Barry.

That was really creative! Not sure I want to edit all my objects in need though. Right now I have saved out a dummy model as pln in which I bluntly move the objects out into the corresponding zones. I'll save your gdl hack for later when there is more time.