<?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 Patches vs library parts in Modeling</title>
    <link>https://community.graphisoft.com/t5/Modeling/Patches-vs-library-parts/m-p/108010#M56893</link>
    <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;What is the difference between these and how one would use them. Is it just that the patch has the opaque option allowing you to cover up things?&lt;/T&gt;&lt;/DIV&gt;</description>
    <pubDate>Fri, 27 Jul 2007 16:01:21 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2007-07-27T16:01:21Z</dc:date>
    <item>
      <title>Patches vs library parts</title>
      <link>https://community.graphisoft.com/t5/Modeling/Patches-vs-library-parts/m-p/108010#M56893</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;What is the difference between these and how one would use them. Is it just that the patch has the opaque option allowing you to cover up things?&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 27 Jul 2007 16:01:21 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Patches-vs-library-parts/m-p/108010#M56893</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2007-07-27T16:01:21Z</dc:date>
    </item>
    <item>
      <title>Re: Patches vs library parts</title>
      <link>https://community.graphisoft.com/t5/Modeling/Patches-vs-library-parts/m-p/108011#M56894</link>
      <description>A patch &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;is&lt;E&gt;&lt;/E&gt; a 2D library part made semi-automatically from your marquee selection in plan.</description>
      <pubDate>Fri, 27 Jul 2007 16:26:54 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Patches-vs-library-parts/m-p/108011#M56894</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2007-07-27T16:26:54Z</dc:date>
    </item>
    <item>
      <title>Re: Patches vs library parts</title>
      <link>https://community.graphisoft.com/t5/Modeling/Patches-vs-library-parts/m-p/108012#M56895</link>
      <description>I was trying to figure out where you would use one rather than the other.</description>
      <pubDate>Mon, 30 Jul 2007 18:33:20 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Patches-vs-library-parts/m-p/108012#M56895</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2007-07-30T18:33:20Z</dc:date>
    </item>
    <item>
      <title>Re: Patches vs library parts</title>
      <link>https://community.graphisoft.com/t5/Modeling/Patches-vs-library-parts/m-p/108013#M56896</link>
      <description>Patch is meant to be a cleanup tool, like if you have a slab/wall/column intersection (say to place bolts and connector plates). You marquee it, make the patch, then make the 2D corrections in the patch.&lt;BR /&gt;
&lt;BR /&gt;
Since the patch has a built-in mask, you can place it over that condition in other sections knowing that if it changes you only have to correct the object.&lt;BR /&gt;
&lt;BR /&gt;
The object tool could be any of thousands of objects, be they toilets, sinks, cabinets, cars, etc.</description>
      <pubDate>Mon, 30 Jul 2007 18:55:13 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/Patches-vs-library-parts/m-p/108013#M56896</guid>
      <dc:creator>TomWaltz</dc:creator>
      <dc:date>2007-07-30T18:55:13Z</dc:date>
    </item>
  </channel>
</rss>

