<?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 Libary parts with anoying bits in Libraries &amp; objects</title>
    <link>https://community.graphisoft.com/t5/Libraries-objects/Libary-parts-with-anoying-bits/m-p/78454#M29610</link>
    <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;I've just rediscovered another AC gripe. Library parts which are perfectly usuable but for annoying bits that spoil them. I'm designing a kitchen and have selected 'hood and vent 11' library part. Looks good but the library part designer had choosen to include control switches directly below the hood, on the RH side. This shows on the elevation. I can't use this object because the switch would sit on the glass splashback and nobdy would choose to do this. Why put it there? Why not make this an option that can or cannot be shown? &lt;BR /&gt;
&lt;BR /&gt;
Please object writers - use your nous!&lt;/T&gt;&lt;/DIV&gt;</description>
    <pubDate>Fri, 09 Nov 2007 01:41:49 GMT</pubDate>
    <dc:creator>KeesW</dc:creator>
    <dc:date>2007-11-09T01:41:49Z</dc:date>
    <item>
      <title>Libary parts with anoying bits</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Libary-parts-with-anoying-bits/m-p/78454#M29610</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;I've just rediscovered another AC gripe. Library parts which are perfectly usuable but for annoying bits that spoil them. I'm designing a kitchen and have selected 'hood and vent 11' library part. Looks good but the library part designer had choosen to include control switches directly below the hood, on the RH side. This shows on the elevation. I can't use this object because the switch would sit on the glass splashback and nobdy would choose to do this. Why put it there? Why not make this an option that can or cannot be shown? &lt;BR /&gt;
&lt;BR /&gt;
Please object writers - use your nous!&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 09 Nov 2007 01:41:49 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Libary-parts-with-anoying-bits/m-p/78454#M29610</guid>
      <dc:creator>KeesW</dc:creator>
      <dc:date>2007-11-09T01:41:49Z</dc:date>
    </item>
    <item>
      <title>Re: Libary parts with anoying bits</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Libary-parts-with-anoying-bits/m-p/78455#M29611</link>
      <description>Hello Kees,&lt;BR /&gt;
Will setting the 3D detail level to "Simple" work for your elevation ?&lt;BR /&gt;
Peter Devlin</description>
      <pubDate>Fri, 09 Nov 2007 02:14:59 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Libary-parts-with-anoying-bits/m-p/78455#M29611</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2007-11-09T02:14:59Z</dc:date>
    </item>
    <item>
      <title>Re: Libary parts with anoying bits</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Libary-parts-with-anoying-bits/m-p/78456#M29612</link>
      <description>Yes thank you Peter - it does work.&lt;BR /&gt;
&lt;BR /&gt;
But why do they do the programmers make make such choices? And what if we want to see it in glorious detail?</description>
      <pubDate>Fri, 09 Nov 2007 06:23:55 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Libary-parts-with-anoying-bits/m-p/78456#M29612</guid>
      <dc:creator>KeesW</dc:creator>
      <dc:date>2007-11-09T06:23:55Z</dc:date>
    </item>
    <item>
      <title>Re: Libary parts with anoying bits</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Libary-parts-with-anoying-bits/m-p/78457#M29613</link>
      <description>Like most real world computer programming failures (IMHO) this is a problem of design and specification. There is often not enough time given to thinking through how things are actually going to be used before they are made. While this can be very difficult it is also vitally important.</description>
      <pubDate>Fri, 09 Nov 2007 18:33:19 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Libary-parts-with-anoying-bits/m-p/78457#M29613</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2007-11-09T18:33:19Z</dc:date>
    </item>
  </channel>
</rss>

