<?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: LPM Grabbing Prior Object Elements Outside Design Area in Libraries &amp; objects</title>
    <link>https://community.graphisoft.com/t5/Libraries-objects/LPM-Grabbing-Prior-Object-Elements-Outside-Design-Area/m-p/622792#M45582</link>
    <description>&lt;P&gt;Well, it appears if I delete the Library Part Name in the LPM toolbox before starting a new object, it will not associate the other elements to it. &amp;nbsp;Still, it is very odd how it highlights everything outside the Design Area. &amp;nbsp;Very confusing. &amp;nbsp;In any case, by clearing the LPM and creating a newly named object (would not work by using the same name in starting over), I was able to keep the two separated.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 15 Aug 2024 01:15:34 GMT</pubDate>
    <dc:creator>Marc H</dc:creator>
    <dc:date>2024-08-15T01:15:34Z</dc:date>
    <item>
      <title>LPM Grabbing Prior Object Elements Outside Design Area</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/LPM-Grabbing-Prior-Object-Elements-Outside-Design-Area/m-p/622790#M45581</link>
      <description>&lt;P&gt;I'm working with the LPM to create some simple objects consisting of two elements. &amp;nbsp;I created the design area and successfully created the first object. &amp;nbsp;I then went to create a second object by adding a library part name and a new design area. &amp;nbsp;Though I created new elements for the second object in the new design area, the LPM is picking up all the elements (in their Component categories) from the first object ! &amp;nbsp; It seems the LPM is not respecting the design area boundary at all. &amp;nbsp;It even overwrote the Preview image of the first object with that of the second. &amp;nbsp;Now, both objects seem to be joined in some strange way.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;GS AC Help and online resources provide no guidance on how to prevent this. &amp;nbsp;What am I doing incorrectly? &amp;nbsp;Do I need to somehow clear the prior name or somehow otherwise start fresh? &amp;nbsp;It seems that has no effect with the attempts so far.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier" color="grey"&gt;Operating system used: &lt;EM&gt;Mac Intel-based Sonoma&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Aug 2024 01:00:33 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/LPM-Grabbing-Prior-Object-Elements-Outside-Design-Area/m-p/622790#M45581</guid>
      <dc:creator>Marc H</dc:creator>
      <dc:date>2024-08-15T01:00:33Z</dc:date>
    </item>
    <item>
      <title>Re: LPM Grabbing Prior Object Elements Outside Design Area</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/LPM-Grabbing-Prior-Object-Elements-Outside-Design-Area/m-p/622792#M45582</link>
      <description>&lt;P&gt;Well, it appears if I delete the Library Part Name in the LPM toolbox before starting a new object, it will not associate the other elements to it. &amp;nbsp;Still, it is very odd how it highlights everything outside the Design Area. &amp;nbsp;Very confusing. &amp;nbsp;In any case, by clearing the LPM and creating a newly named object (would not work by using the same name in starting over), I was able to keep the two separated.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Aug 2024 01:15:34 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/LPM-Grabbing-Prior-Object-Elements-Outside-Design-Area/m-p/622792#M45582</guid>
      <dc:creator>Marc H</dc:creator>
      <dc:date>2024-08-15T01:15:34Z</dc:date>
    </item>
  </channel>
</rss>

