<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Zone Tags Content Visibility Control in Documentation</title>
    <link>https://community.graphisoft.com/t5/Documentation/Zone-Tags-Content-Visibility-Control/m-p/309453#M48143</link>
    <description>&lt;P&gt;Is it possible to control what content is shown in a zone tag via layers or another way outside of scale?&amp;nbsp; For example, I've got three plans all at the same scale (code plan, floor plan, finish plan), but only the code plan&amp;nbsp; requires information on area and occupant loading.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Right now it's looking like I have to do one of the following to make it work.&lt;/P&gt;&lt;P&gt;1. Duplicate the zones and put them on a layer that's only visible for the code plan.&amp;nbsp; The issue here is added redundancy &amp;amp; then another item to QA later on.&lt;/P&gt;&lt;P&gt;2. Add text boxes for area and occupant load separate from the zones that only show up on the code plan.&amp;nbsp; Downside here is the manual entry &amp;amp; update.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;</description>
    <pubDate>Thu, 18 May 2023 11:10:21 GMT</pubDate>
    <dc:creator>MlMcc</dc:creator>
    <dc:date>2023-05-18T11:10:21Z</dc:date>
    <item>
      <title>Zone Tags Content Visibility Control</title>
      <link>https://community.graphisoft.com/t5/Documentation/Zone-Tags-Content-Visibility-Control/m-p/309453#M48143</link>
      <description>&lt;P&gt;Is it possible to control what content is shown in a zone tag via layers or another way outside of scale?&amp;nbsp; For example, I've got three plans all at the same scale (code plan, floor plan, finish plan), but only the code plan&amp;nbsp; requires information on area and occupant loading.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Right now it's looking like I have to do one of the following to make it work.&lt;/P&gt;&lt;P&gt;1. Duplicate the zones and put them on a layer that's only visible for the code plan.&amp;nbsp; The issue here is added redundancy &amp;amp; then another item to QA later on.&lt;/P&gt;&lt;P&gt;2. Add text boxes for area and occupant load separate from the zones that only show up on the code plan.&amp;nbsp; Downside here is the manual entry &amp;amp; update.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Thu, 18 May 2023 11:10:21 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Zone-Tags-Content-Visibility-Control/m-p/309453#M48143</guid>
      <dc:creator>MlMcc</dc:creator>
      <dc:date>2023-05-18T11:10:21Z</dc:date>
    </item>
    <item>
      <title>Re: Zone Tags Content Visibility Control</title>
      <link>https://community.graphisoft.com/t5/Documentation/Zone-Tags-Content-Visibility-Control/m-p/309535#M48167</link>
      <description>&lt;P&gt;How good are your GDL skills?&lt;/P&gt;
&lt;P&gt;As you already know, you need to be able to recognise which plan is being viewed.&lt;/P&gt;
&lt;P&gt;There was some 'request' (I think from memory - long time since I have tried it) that was to do with layer, but I never had any success with it - so used the scale trick.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However, we now have Library Globals.&lt;/P&gt;
&lt;P&gt;These are values which can be set in the Model View Options.&lt;/P&gt;
&lt;P&gt;So, if you have a different MVO saved with each plan view, you can have a different value set for your Library Global in each MVO that will control the zone stamp.&lt;/P&gt;
&lt;P&gt;For example, you would create a Library Global that could simply be an on/off boolean value to say 'show area and occupancy loading'.&lt;/P&gt;
&lt;P&gt;Therefore you will be able to recognise which plan is being used and can then control what is displayed by the zone stamp.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Barry.&lt;/P&gt;</description>
      <pubDate>Mon, 18 Oct 2021 01:13:34 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Zone-Tags-Content-Visibility-Control/m-p/309535#M48167</guid>
      <dc:creator>Barry Kelly</dc:creator>
      <dc:date>2021-10-18T01:13:34Z</dc:date>
    </item>
    <item>
      <title>Re: Zone Tags Content Visibility Control</title>
      <link>https://community.graphisoft.com/t5/Documentation/Zone-Tags-Content-Visibility-Control/m-p/309641#M48214</link>
      <description>&lt;P&gt;Well at this point, non-existent.&amp;nbsp; I'm very new to the program and have no background in scripting.&amp;nbsp; But, this sounds like exactly what we need, so time to figure it out.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I do have an MVO specific to code plans as there are other uniques for that plan requiring management and the simple boolean function is all I need.&amp;nbsp; If you have any suggestions for resources on how to learn to create Library Globals, I'll take it.&lt;/P&gt;</description>
      <pubDate>Mon, 18 Oct 2021 20:15:14 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Zone-Tags-Content-Visibility-Control/m-p/309641#M48214</guid>
      <dc:creator>MlMcc</dc:creator>
      <dc:date>2021-10-18T20:15:14Z</dc:date>
    </item>
    <item>
      <title>Re: Zone Tags Content Visibility Control</title>
      <link>https://community.graphisoft.com/t5/Documentation/Zone-Tags-Content-Visibility-Control/m-p/309673#M48228</link>
      <description>&lt;P&gt;It is a little involved and took me a while to get my head around it.&lt;/P&gt;
&lt;P&gt;So for someone with no GDL knowledge it may be a little intense.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Just search +Library +Globals here and you will see a few posts on the subject.&lt;/P&gt;
&lt;P&gt;I don't have time to go through and find any that might be about creating library Globals.&lt;/P&gt;
&lt;P&gt;It will also require editing the zone stamp as well.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If I spot something that explains it well, I will post back here.&lt;/P&gt;
&lt;P&gt;If anyone has or knows of something that explains this clearly, please add your knowledge.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Barry.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Oct 2021 02:28:40 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Zone-Tags-Content-Visibility-Control/m-p/309673#M48228</guid>
      <dc:creator>Barry Kelly</dc:creator>
      <dc:date>2021-10-19T02:28:40Z</dc:date>
    </item>
    <item>
      <title>Re: Zone Tags Content Visibility Control</title>
      <link>https://community.graphisoft.com/t5/Documentation/Zone-Tags-Content-Visibility-Control/m-p/309743#M48241</link>
      <description>&lt;P&gt;Thank you!&amp;nbsp; I started looking into it and it's probably a future add to our template as we work on improving our skills.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Oct 2021 17:14:02 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/Zone-Tags-Content-Visibility-Control/m-p/309743#M48241</guid>
      <dc:creator>MlMcc</dc:creator>
      <dc:date>2021-10-19T17:14:02Z</dc:date>
    </item>
  </channel>
</rss>

