17 hours ago
I am designing a custom zone label, to be a jack of all trades. I am interested if it's possible to read the current GO or if a GO is on, so i can display some data based on this.
I am basicaly trying to display the occupancy property of a zone only on the fire plan graphic override.
Solved! Go to Solution.
16 hours ago
It never hurts to have multiple options, but it can get confusing for the operator.
Just thinking, if you can't determine if a GO is active, you could use Library Globals and Model View Options.
You would need to create a new MVO parameter for 'fire plan - on/off'.
Then a new MVO combination for fire plans where that option is on (off for all other MVO combinations).
Your label can then read the MVO parameter setting and adjust accordingly.
Barry.
17 hours ago
I don't have an answer to your question.
But wouldn't it just be better/easier to place the zone label on a layer that is active for the fire plan?
That way you can position it exactly where you want for that plan (may be a different position to the other plans), and it can show exactly the information that you want independent of other zone labels in other layers.
That is the beauty of labels - you can have as many as you want, in any layer, in different positions and showing different information.
You don't have to rely on one label.
Barry.
17 hours ago
Thanks for your reply. That's how i'm doing it now, but it would be so much easier to use the same label to display that 1 extra row. You need to do double the work to move the labels to dodge the furniture and dimension lines/text every time there are changes involved.
17 hours ago
@insideru wrote:
You need to do double the work to move the labels to dodge the furniture and dimension lines/text every time there are changes involved.
You could also say it is extra work trying to find that one position for the one label that suits all plans.
Of course it would be dependent on the type of plans you are producing.
There is never one way to do something correctly.
Barry.
16 hours ago
You are correct. I am in the process of updating my template after 4 years or so and i'm exploring ideas to speed up my workflow. I started dabbling in GDL and found some ways to achieve that. Maybe i got overexcited 🙂 You gotta admit options are always nice tho, you can try more ways to achieve the same goal and choose the one that works best for you.
16 hours ago
It never hurts to have multiple options, but it can get confusing for the operator.
Just thinking, if you can't determine if a GO is active, you could use Library Globals and Model View Options.
You would need to create a new MVO parameter for 'fire plan - on/off'.
Then a new MVO combination for fire plans where that option is on (off for all other MVO combinations).
Your label can then read the MVO parameter setting and adjust accordingly.
Barry.
8 hours ago
That is an excellent take i hadn't thought about.
Thanks