<?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 modifying library parts in Modeling</title>
    <link>https://community.graphisoft.com/t5/Modeling/modifying-library-parts/m-p/54633#M27684</link>
    <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;One of the issues you run into when using a Graphisoft library part in an office library is that there are Macros (sub-objects) that are probably required as well. the trick is to go through the object and look for CALL commands and make sure that you get all the objects that are called from inside the detail marker.&lt;/T&gt;&lt;/DIV&gt;</description>
    <pubDate>Tue, 23 May 2023 15:14:05 GMT</pubDate>
    <dc:creator>TomWaltz</dc:creator>
    <dc:date>2023-05-23T15:14:05Z</dc:date>
    <item>
      <title>modifying library parts</title>
      <link>https://community.graphisoft.com/t5/Modeling/modifying-library-parts/m-p/54633#M27684</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;One of the issues you run into when using a Graphisoft library part in an office library is that there are Macros (sub-objects) that are probably required as well. the trick is to go through the object and look for CALL commands and make sure that you get all the objects that are called from inside the detail marker.&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 23 May 2023 15:14:05 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Modeling/modifying-library-parts/m-p/54633#M27684</guid>
      <dc:creator>TomWaltz</dc:creator>
      <dc:date>2023-05-23T15:14:05Z</dc:date>
    </item>
  </channel>
</rss>

