2022-11-09 01:25 PM
I'm working on a "Empty Window" to place over a Graphisoft window to add some extra functionality like wallclosure in 3D. But now a zones add up the Window Surface of both windows place on top of eachother.
I thought changing the ac_zone_on_reveal_side and gs_bOpeningToZone parameters might do something but they don't seem to in regards to window surface.
Is there a way to completely exclude the empty window?
Solved! Go to Solution.
2022-11-09 01:52 PM
If you create a property for your windows that calculates the surface, you can create a schedule to add these up and exclude the empty window by something simple like element ID.
Not sure if you can easily tie this in to zones if you need to know it on a per room basis.
2022-11-10 02:36 AM
As Erwin mentioned, give you opening an ID of something like "Ignore".
Then it the schedule criteria, you set it up to look for all windows with an ID is not "Ignore".
2022-12-01 11:42 AM
That's a shame. I worked my way around it by replacing A & B with AC_Reveal_Width / Height and then setting B to 0 and locking both A & B.
If you set A to 0 the Wallhole2 function doesn't work anymore.
What's a shame is that the automatic hotspots for A & B to change the size by draging don't work anymore.
Would be useful for Graphisoft to create a glob parameter for windows with which it can be ignored by zones. I've been using windows more and more for things other then "windows" like niches or built-in Wardrobes.
Dankjewel anyway 🙂
2022-12-01 03:27 PM - edited 2022-12-01 03:27 PM
As Barry pointed out the schedule doesn't have to be any more complex than this:
I forgot that you can grab surface from windows as a field without using properties, since it is already one of the (many) options of data you can grab from windows.