<?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 call objects shortcut in Libraries &amp; objects</title>
    <link>https://community.graphisoft.com/t5/Libraries-objects/call-objects-shortcut/m-p/4223#M41669</link>
    <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;when i to use "call " command for an object ( macro) with too many parameters i usually put this object in plan i save it again temporary to the desktop and i open the new archicad written object  to get job done with copy and paste , modify only &lt;BR /&gt;
the "..."  values with the parametric one&lt;/T&gt;&lt;/DIV&gt;</description>
    <pubDate>Mon, 08 Dec 2003 20:29:10 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2003-12-08T20:29:10Z</dc:date>
    <item>
      <title>call objects shortcut</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/call-objects-shortcut/m-p/4223#M41669</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;when i to use "call " command for an object ( macro) with too many parameters i usually put this object in plan i save it again temporary to the desktop and i open the new archicad written object  to get job done with copy and paste , modify only &lt;BR /&gt;
the "..."  values with the parametric one&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 08 Dec 2003 20:29:10 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/call-objects-shortcut/m-p/4223#M41669</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2003-12-08T20:29:10Z</dc:date>
    </item>
    <item>
      <title>Re: call objects shortcut</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/call-objects-shortcut/m-p/4224#M41670</link>
      <description>Skip the "call" and just copy and paste the scripts into a single object script it will save a lot of hassles in the future. I find that for the amount of editing and trouble shooting one must do it's simply not worth using macros.</description>
      <pubDate>Tue, 23 Dec 2003 00:28:53 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/call-objects-shortcut/m-p/4224#M41670</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2003-12-23T00:28:53Z</dc:date>
    </item>
    <item>
      <title>Re: call objects shortcut</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/call-objects-shortcut/m-p/4225#M41671</link>
      <description>If you want a single object that is portable, i agree that macros are a pain. &lt;BR /&gt;
   But if you are building a library for a commercial use, eg windows or industrialised components, where certain things are used on different primary objects, and you want to locate exactly where editing of changes can take place, then macros are very important.&lt;BR /&gt;
&lt;BR /&gt;

&lt;BLOCKQUOTE&gt;Jeffrey wrote:&lt;BR /&gt;Skip the "call" and just copy and paste the scripts into a single object script it will save a lot of hassles in the future. I find that for the amount of editing and trouble shooting one must do it's simply not worth using macros.&lt;/BLOCKQUOTE&gt;</description>
      <pubDate>Mon, 29 Dec 2003 00:28:14 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/call-objects-shortcut/m-p/4225#M41671</guid>
      <dc:creator>david nicholson-cole</dc:creator>
      <dc:date>2003-12-29T00:28:14Z</dc:date>
    </item>
  </channel>
</rss>

