<?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 Re: So we are never going to be able to control element visibility with GO? in Documentation</title>
    <link>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/384132#M60969</link>
    <description>&lt;P&gt;That's truly happened in second Q&amp;amp;A session, I and others asked if we have design options why we still can't hide element in 2D plan??&lt;/P&gt;
&lt;P&gt;The answer was from&amp;nbsp;&lt;a href="https://community.graphisoft.com/t5/user/viewprofilepage/user-id/8383"&gt;@Marton Kiss&lt;/a&gt;&amp;nbsp;proves that GS is interested in hiding elements by layers and said something about a quiz he had before when he was at school I personally couldn't understand well either this quiz or the logic behind hiding layers not elements cuz they were hurry and speaking fast.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Even I'm surprised why Q&amp;amp;A sessions are not uploaded to the events' videos yet despite the same session in collaborate event is exist!!&lt;/P&gt;</description>
    <pubDate>Sun, 18 Jun 2023 08:12:32 GMT</pubDate>
    <dc:creator>Mahmoud Qenawi</dc:creator>
    <dc:date>2023-06-18T08:12:32Z</dc:date>
    <item>
      <title>So we are never going to be able to control element visibility with GO?</title>
      <link>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/383867#M60955</link>
      <description>&lt;P&gt;So GS just confirmed in their event that they are not interested in developing the Graphic over ride function to control element visibility because they think that it is to hard for AC users to get our heads around. Seriously!!! We are the ones asking for it. Visibility by layers only is old fashioned and ignores the value that properties &amp;amp; classifications embeds in the element.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Jun 2023 14:38:33 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/383867#M60955</guid>
      <dc:creator>gavinNZz</dc:creator>
      <dc:date>2023-06-15T14:38:33Z</dc:date>
    </item>
    <item>
      <title>Re: So we are never going to be able to control element visibility with GO?</title>
      <link>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/383896#M60957</link>
      <description>&lt;P&gt;I personally don't think that controlling it through GO is a good end solution as there should be a distinction between what element is visible/active and how it is graphically represented. But the introduction of truly invisible lines/surfaces/fills would be a quick fix with minimum "confusion" for users.&amp;nbsp; &lt;BR /&gt;&lt;BR /&gt;I didn't see the Q&amp;amp;A but if the answer was to be understood as GS sticking with the current layer-based visibility control for the foreseeable future it sure is depressing.&amp;nbsp;Currently visibility control is all over the place and in urgent need of an effort to consolidate/harmonise/centralise. A &lt;A href="https://community.graphisoft.com/t5/Wishes/Element-Visibility-Control/td-p/309163" target="_self"&gt;criteria based approach&lt;/A&gt; would enable just that and at the same time making sure that AC is keeping up with the development, enabling truly object oriented workflows.&lt;/P&gt;</description>
      <pubDate>Thu, 15 Jun 2023 18:30:08 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/383896#M60957</guid>
      <dc:creator>hevi</dc:creator>
      <dc:date>2023-06-15T18:30:08Z</dc:date>
    </item>
    <item>
      <title>Re: So we are never going to be able to control element visibility with GO?</title>
      <link>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/384126#M60968</link>
      <description>&lt;P&gt;Agree. It is truly depressing GS still thinks layer based visibility control is still the best way for users.&lt;/P&gt;</description>
      <pubDate>Sun, 18 Jun 2023 02:33:07 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/384126#M60968</guid>
      <dc:creator>Scraptrash</dc:creator>
      <dc:date>2023-06-18T02:33:07Z</dc:date>
    </item>
    <item>
      <title>Re: So we are never going to be able to control element visibility with GO?</title>
      <link>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/384132#M60969</link>
      <description>&lt;P&gt;That's truly happened in second Q&amp;amp;A session, I and others asked if we have design options why we still can't hide element in 2D plan??&lt;/P&gt;
&lt;P&gt;The answer was from&amp;nbsp;&lt;a href="https://community.graphisoft.com/t5/user/viewprofilepage/user-id/8383"&gt;@Marton Kiss&lt;/a&gt;&amp;nbsp;proves that GS is interested in hiding elements by layers and said something about a quiz he had before when he was at school I personally couldn't understand well either this quiz or the logic behind hiding layers not elements cuz they were hurry and speaking fast.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Even I'm surprised why Q&amp;amp;A sessions are not uploaded to the events' videos yet despite the same session in collaborate event is exist!!&lt;/P&gt;</description>
      <pubDate>Sun, 18 Jun 2023 08:12:32 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/384132#M60969</guid>
      <dc:creator>Mahmoud Qenawi</dc:creator>
      <dc:date>2023-06-18T08:12:32Z</dc:date>
    </item>
    <item>
      <title>Re: So we are never going to be able to control element visibility with GO?</title>
      <link>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/392921#M61237</link>
      <description>&lt;P&gt;Thanks graphisoft for publishing the Q&amp;amp;A session related to Design Building Together event.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jul 2023 02:08:45 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/392921#M61237</guid>
      <dc:creator>Mahmoud Qenawi</dc:creator>
      <dc:date>2023-07-21T02:08:45Z</dc:date>
    </item>
    <item>
      <title>Re: So we are never going to be able to control element visibility with GO?</title>
      <link>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393192#M61245</link>
      <description>&lt;P&gt;Setting up a GO rule to hide a specific element seems just as convoluted as making a new layer + layer combination to me.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Model View Options and Floor Plan Range usually do the trick and you can set most elements to 'ignore' MVO and use a custom setting for the odd ones out.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can you give a specific case of what you need to hide based on properties?&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jul 2023 08:05:22 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393192#M61245</guid>
      <dc:creator>Erwin Edel</dc:creator>
      <dc:date>2023-07-24T08:05:22Z</dc:date>
    </item>
    <item>
      <title>Re: So we are never going to be able to control element visibility with GO?</title>
      <link>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393206#M61247</link>
      <description>&lt;P&gt;Hiding elements via GO is achievable, but personally I think it the wrong place if you wish for an on/off status. I have already raised a wish for transparency and fade in GOs, but that is from my view aimed at graphical presentation.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;a href="https://community.graphisoft.com/t5/user/viewprofilepage/user-id/3332"&gt;@Erwin Edel&lt;/a&gt;&amp;nbsp;comments above are valid in the current AC display arrangement, but I do think controlling on/off by criteria / attributes is a better place for development of such a feature and would be a lot easier to manage than using GOs. I did advocate that such a provision could have taken Design Options to a far more advanced level, but as ever we have a solution with limited usability.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jul 2023 11:15:03 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393206#M61247</guid>
      <dc:creator>DGSketcher</dc:creator>
      <dc:date>2023-07-24T11:15:03Z</dc:date>
    </item>
    <item>
      <title>Re: So we are never going to be able to control element visibility with GO?</title>
      <link>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393208#M61249</link>
      <description>&lt;P&gt;Could/Should adding these criteria to Layers instead of GOs be the option?&lt;/P&gt;
&lt;P&gt;Having the existing Layer Palette be the Basic Layer Manager and then having a "Expert" Layer Manager were you could have rule based Master Layers might keep AC simple for new users while giving us extra control.&lt;/P&gt;
&lt;P&gt;Layers, control Model vs GOs, control Graphics?&lt;/P&gt;
&lt;P&gt;--&lt;/P&gt;
&lt;P&gt;and if this works then Pen Settings might be integrated into GO's to be the Basic UI and GO rules go into Expert Mode…?&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jul 2023 11:46:19 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393208#M61249</guid>
      <dc:creator>Eduardo Rolon</dc:creator>
      <dc:date>2023-07-24T11:46:19Z</dc:date>
    </item>
    <item>
      <title>Re: So we are never going to be able to control element visibility with GO?</title>
      <link>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393220#M61250</link>
      <description>&lt;P&gt;I know you know all this &lt;a href="https://community.graphisoft.com/t5/user/viewprofilepage/user-id/3018"&gt;@Eduardo Rolon&lt;/a&gt;&amp;nbsp;, but for those less familiar... As I have tried to explain in various places, Layers are just another attribute of an Element. The key fact is under a BIM workflow, each Element is assigned multiple attributes. The obvious ones which are common to every Element are...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;ID&lt;/P&gt;
&lt;P&gt;Layer&lt;/P&gt;
&lt;P&gt;Renovation Status&lt;/P&gt;
&lt;P&gt;Design Option (new)&lt;/P&gt;
&lt;P&gt;Structural Function&lt;/P&gt;
&lt;P&gt;Position&lt;/P&gt;
&lt;P&gt;IFC Properties...&lt;/P&gt;
&lt;P&gt;the less obvious material type Core, Finish &amp;amp; Other&amp;nbsp;&lt;/P&gt;
&lt;P&gt;and then we have Classifications which when used to control the displayed elements opens a multitude of possibilities e.g. filtering by your preferred classification system e.g. Uniclass, CAWS etc.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;All these attribute are permanently active and we use them to determine the presentation of each Element. Yes we can use GO, but supposing I want to just display or export Elements assigned to an attribute e.g. Load bearing, or just the External Elements or an IFC Type, or more interestingly those assigned to a custom classification such as Phase 3! Within the current scope there is no easy way to filter what is presented without potentially developing long lists of layers, which come with an increased risk of layer assignment error as the lists get ever longer. I can appreciate for many, this approach may appear more complex than just Layers, but for the future and definitely for 3D modelling we need to move beyond the current limitations of Layered presentation and start leveraging the potential of 3D &amp;amp; BIM.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Could/ Should this be achieved by a criteria / rules based display system or a simple Layer type on/off system with sub-folders that lets you add attributes &amp;amp; classifications and save them in combinations? - Personally anything would be better than the piecemeal blinkered approach that has landed with a bang with Design Options.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I think from the manual VW has Classification control, it would be interesting to hear how users are leveraging that workflow?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jul 2023 14:28:49 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393220#M61250</guid>
      <dc:creator>DGSketcher</dc:creator>
      <dc:date>2023-07-24T14:28:49Z</dc:date>
    </item>
    <item>
      <title>Re: So we are never going to be able to control element visibility with GO?</title>
      <link>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393234#M61251</link>
      <description>&lt;P&gt;&lt;a href="https://community.graphisoft.com/t5/user/viewprofilepage/user-id/11396"&gt;@DGSketcher&lt;/a&gt;&amp;nbsp;We are in agreement, just thinking how to organize the "Saved Views" so that it is easy to teach to new users.&lt;/P&gt;
&lt;P&gt;My emphasis is trying to keep it as simple as possible&lt;/P&gt;
&lt;P&gt;If we add rules to Layers then GS has to integrate them with Properties/Classifications et al. which is a necessary wish&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Main Controls: All Project Types
&lt;UL&gt;
&lt;LI&gt;What is displayed from the model = On/Off (other layer settings) controlled by Layer Rules&lt;/LI&gt;
&lt;LI&gt;How the model is displayed = Display/Print is controlled by GOs&lt;/LI&gt;
&lt;LI&gt;Graphic Standards and Scale Sensitivity (LOD?) = &amp;nbsp;Model View Options&lt;/LI&gt;
&lt;LI&gt;Design Options&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;Secondary Controls: depends on project type
&lt;UL&gt;
&lt;LI&gt;Renovation&lt;/LI&gt;
&lt;LI&gt;Phasing&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;Layout Set Controls (How Drawings are Defined):
&lt;UL&gt;
&lt;LI&gt;Scale&lt;/LI&gt;
&lt;LI&gt;Pen Set&lt;/LI&gt;
&lt;LI&gt;…&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jul 2023 18:09:03 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393234#M61251</guid>
      <dc:creator>Eduardo Rolon</dc:creator>
      <dc:date>2023-07-24T18:09:03Z</dc:date>
    </item>
    <item>
      <title>Re: So we are never going to be able to control element visibility with GO?</title>
      <link>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393243#M61252</link>
      <description>&lt;P&gt;If it is to be kept simple then I think the bit that GS missed with Design Options is the potential of Display by Class to make the separate controls for Design Options, Renovation &amp;amp; Material Type (Core, finish etc) redundant. That action alone would make AC easier to use, moving the "I can't see..." options from multiple to a single point.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Classification Manager will host any number of "Systems". You want Phasing, you add a System and you can display one phase, multiple or all phases in any combination you want. The same would apply to Design Options &amp;amp; Renovation. A Material Type class would finally resolve those situations where Morphs fail to respond to Partial Structure Display because they can't be designated as a Finish etc.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;And just like GOs that came with an immediate wow factor when introduced, Display by Class could be a simple expandable tool that can be ignored by Beginners, Easy to follow for most Users and extremely powerful in the hands of an Advanced User that needs to collaborate by filtering and exporting 3D models.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jul 2023 17:33:16 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393243#M61252</guid>
      <dc:creator>DGSketcher</dc:creator>
      <dc:date>2023-07-24T17:33:16Z</dc:date>
    </item>
    <item>
      <title>Re: So we are never going to be able to control element visibility with GO?</title>
      <link>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393300#M61262</link>
      <description>&lt;P&gt;I only have experience with the Dutch NL-sfb classification system, but it uses chapters and paragraphs and basically 99% of modelling layers are the chapter numbers. For example chapter 21 is "exterior walls", you draft all exterior walls on that layer ("21 exterior walls") and then you can go in to the paragraphs with the classification system, for example 21.22 "structural cavity wall". With this system layers work extremely well to filter elements for classification.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Maybe this is why I am unfamiliar with these filtering problems.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The only thing I really miss, is being able to set 'finish' or 'other' to elements that only use a single building material as structure.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jul 2023 07:27:49 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393300#M61262</guid>
      <dc:creator>Erwin Edel</dc:creator>
      <dc:date>2023-07-25T07:27:49Z</dc:date>
    </item>
    <item>
      <title>Re: So we are never going to be able to control element visibility with GO?</title>
      <link>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393575#M61292</link>
      <description>&lt;P&gt;If we went down the fusion of criteria &amp;amp; classification to control visibility, one other attribute that would require consideration is the current Layer Intersection Number. I can see situations where you may want to override the value assigned to a layer. So perhaps like GOs, apart from changing an elements visibility from on/off it would also optionally override intersection numbers.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jul 2023 09:44:02 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393575#M61292</guid>
      <dc:creator>DGSketcher</dc:creator>
      <dc:date>2023-07-27T09:44:02Z</dc:date>
    </item>
    <item>
      <title>Re: So we are never going to be able to control element visibility with GO?</title>
      <link>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393617#M61293</link>
      <description>&lt;P&gt;&lt;EM&gt;&lt;a href="https://community.graphisoft.com/t5/user/viewprofilepage/user-id/3332"&gt;@Erwin Edel&lt;/a&gt;&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;"The only thing I really miss, is being able to set 'finish' or 'other' to elements that only use a single building material as structure."&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I found&amp;nbsp;&lt;a href="https://community.graphisoft.com/t5/user/viewprofilepage/user-id/7331"&gt;@Barry Kelly&lt;/a&gt;&amp;nbsp;writing this in another post replying to your request :&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="0EAD1C4F-A197-4BBC-B8CD-9017022B45A0.jpeg" style="width: 1242px;"&gt;&lt;img src="https://community.graphisoft.com/t5/image/serverpage/image-id/44088iA962B2E263673123/image-size/medium?v=v2&amp;amp;px=400" role="button" title="0EAD1C4F-A197-4BBC-B8CD-9017022B45A0.jpeg" alt="0EAD1C4F-A197-4BBC-B8CD-9017022B45A0.jpeg" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt; I hope that's what you hope for.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jul 2023 20:10:37 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393617#M61293</guid>
      <dc:creator>Mahmoud Qenawi</dc:creator>
      <dc:date>2023-07-27T20:10:37Z</dc:date>
    </item>
    <item>
      <title>Re: So we are never going to be able to control element visibility with GO?</title>
      <link>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393624#M61296</link>
      <description>&lt;P&gt;That post may be being viewed out of context. As&amp;nbsp;&lt;a href="https://community.graphisoft.com/t5/user/viewprofilepage/user-id/3332"&gt;@Erwin Edel&lt;/a&gt;&amp;nbsp;indicated, any Element that uses a single building material requires a work around to assign the core / finish / other attribute. In many cases you can assign a Composite or Complex Profile, but there are elements like Morphs &amp;amp; Meshes where you can't and the general assignment of using the basic tools such as beams, columns, walls etc and assigning the material status in the tool isn't an option. The Material Status could be assigned in the Building Material definition, then it wouldn't matter if you used a single material, complex profile or a composite, the material definition for Partial Structure Display would be automatic, but to be fair to GS that is going to need a MAJOR program update.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Given the growing dependence on Morphs for complex shapes to get around SEO failures, perhaps there could be a way to assign the Material Status in the tool. I have set up a &lt;A href="https://community.graphisoft.com/t5/Wishes/Add-Material-Status-attribute-to-Morphs-amp-Meshes/m-p/393623#M23448" target="_self"&gt;WISH&lt;/A&gt;&amp;nbsp;for this.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jul 2023 21:58:00 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393624#M61296</guid>
      <dc:creator>DGSketcher</dc:creator>
      <dc:date>2023-07-27T21:58:00Z</dc:date>
    </item>
    <item>
      <title>Re: So we are never going to be able to control element visibility with GO?</title>
      <link>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393842#M61307</link>
      <description>&lt;P&gt;Some simple elements shouldn't need a composite for every single thickness or a stretchy complex profile, just because I need them to not be 'core'.&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jul 2023 06:55:01 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/So-we-are-never-going-to-be-able-to-control-element-visibility/m-p/393842#M61307</guid>
      <dc:creator>Erwin Edel</dc:creator>
      <dc:date>2023-07-31T06:55:01Z</dc:date>
    </item>
  </channel>
</rss>

