<?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 SEO in plan update in Modeling</title>
    <link>https://community.graphisoft.com/t5/Modeling/SEO-in-plan-update/m-p/218175#M118481</link>
    <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Hi there - is it still the case that SEO operations aren't reflected in plan view?&lt;BR /&gt;
&lt;BR /&gt;
Pretty hefty limitation.&lt;BR /&gt;
&lt;BR /&gt;
Anyone got a work around?&lt;BR /&gt;
&lt;BR /&gt;
Cheers&lt;/T&gt;&lt;/DIV&gt;</description>
    <pubDate>Wed, 24 May 2023 17:57:57 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2023-05-24T17:57:57Z</dc:date>
    <item>
      <title>SEO in plan update</title>
      <link>https://community.graphisoft.com/t5/Modeling/SEO-in-plan-update/m-p/218175#M118481</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Hi there - is it still the case that SEO operations aren't reflected in plan view?&lt;BR /&gt;
&lt;BR /&gt;
Pretty hefty limitation.&lt;BR /&gt;
&lt;BR /&gt;
Anyone got a work around?&lt;BR /&gt;
&lt;BR /&gt;
Cheers&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 24 May 2023 17:57:57 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/SEO-in-plan-update/m-p/218175#M118481</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-05-24T17:57:57Z</dc:date>
    </item>
    <item>
      <title>Re: SEO in plan update</title>
      <link>https://community.graphisoft.com/t5/Modeling/SEO-in-plan-update/m-p/218176#M118482</link>
      <description>For plan views, where you use a slab to trim upward, make the trimming element opaque and display it in front of the trimmed element - it masks the trimmed parts.&lt;BR /&gt;
&lt;BR /&gt;
For complex or diagonal trims, make the cut element an object, saving the original parts on invisible layers.</description>
      <pubDate>Sat, 26 Jan 2013 17:29:12 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/SEO-in-plan-update/m-p/218176#M118482</guid>
      <dc:creator>Dwight</dc:creator>
      <dc:date>2013-01-26T17:29:12Z</dc:date>
    </item>
    <item>
      <title>Re: SEO in plan update</title>
      <link>https://community.graphisoft.com/t5/Modeling/SEO-in-plan-update/m-p/218177#M118483</link>
      <description>It depends on what you are SEOing.&lt;BR /&gt;
Multi-plane roofs, shells and morphs display a plan view of the 3D model so SEOs will appear correctly in plan.&lt;BR /&gt;
Walls, slabs, beams and columns do not use this plan view so SEOs on those elements don't appear correctly in plan.&lt;BR /&gt;
Maybe oneday these tools will be updated like the roof tool was.&lt;BR /&gt;
Barry.</description>
      <pubDate>Tue, 29 Jan 2013 02:17:33 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/SEO-in-plan-update/m-p/218177#M118483</guid>
      <dc:creator>Barry Kelly</dc:creator>
      <dc:date>2013-01-29T02:17:33Z</dc:date>
    </item>
  </channel>
</rss>

