<?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 CONCEPT GHOST story in Documentation</title>
    <link>https://community.graphisoft.com/t5/Documentation/CONCEPT-GHOST-story/m-p/2480#M67238</link>
    <description>&lt;DIV class="actalk-migrated-content"&gt;You can do at an inferior story -the main building concept ghost story -in 2d figures lines hatches - for easy compare the global initial ideea with the working solution.&lt;BR /&gt;And i use allways another 0,00 m height ghost story for 2d undesirable but 3d necessary elements between every 2 project story .&lt;BR /&gt;In this way i keep 2d clean plans for the documentation.&lt;/DIV&gt;</description>
    <pubDate>Tue, 04 Feb 2025 14:49:17 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2025-02-04T14:49:17Z</dc:date>
    <item>
      <title>CONCEPT GHOST story</title>
      <link>https://community.graphisoft.com/t5/Documentation/CONCEPT-GHOST-story/m-p/2480#M67238</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;You can do at an inferior story -the main building concept ghost story -in 2d figures lines hatches - for easy compare the global initial ideea with the working solution.&lt;BR /&gt;And i use allways another 0,00 m height ghost story for 2d undesirable but 3d necessary elements between every 2 project story .&lt;BR /&gt;In this way i keep 2d clean plans for the documentation.&lt;/DIV&gt;</description>
      <pubDate>Tue, 04 Feb 2025 14:49:17 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Documentation/CONCEPT-GHOST-story/m-p/2480#M67238</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2025-02-04T14:49:17Z</dc:date>
    </item>
  </channel>
</rss>

