<?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 Passing parameters to macros and effectivity in Libraries &amp; objects</title>
    <link>https://community.graphisoft.com/t5/Libraries-objects/Passing-parameters-to-macros-and-effectivity/m-p/181121#M21496</link>
    <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Hello all,&lt;BR /&gt;
How much does the nested macro calls affect the responsiveness of the object?&lt;BR /&gt;
I mean that if you have ten arrays of [50][150] in the first objects and you pass them to the first macro and then to the nested second macro, does such operations take more memory and time than if you would try to limit the arrays passed to the subobjects?&lt;BR /&gt;
(like 10 items of one dim array of [150] instead of 10 items of [50][150] )&lt;BR /&gt;
&lt;BR /&gt;
Hope I'm clear enough&lt;BR /&gt;
&lt;BR /&gt;
Thanks in advance,&lt;BR /&gt;
Olivier&lt;/T&gt;&lt;/DIV&gt;</description>
    <pubDate>Tue, 02 Feb 2010 10:26:59 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2010-02-02T10:26:59Z</dc:date>
    <item>
      <title>Passing parameters to macros and effectivity</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Passing-parameters-to-macros-and-effectivity/m-p/181121#M21496</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;T&gt;Hello all,&lt;BR /&gt;
How much does the nested macro calls affect the responsiveness of the object?&lt;BR /&gt;
I mean that if you have ten arrays of [50][150] in the first objects and you pass them to the first macro and then to the nested second macro, does such operations take more memory and time than if you would try to limit the arrays passed to the subobjects?&lt;BR /&gt;
(like 10 items of one dim array of [150] instead of 10 items of [50][150] )&lt;BR /&gt;
&lt;BR /&gt;
Hope I'm clear enough&lt;BR /&gt;
&lt;BR /&gt;
Thanks in advance,&lt;BR /&gt;
Olivier&lt;/T&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 02 Feb 2010 10:26:59 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Passing-parameters-to-macros-and-effectivity/m-p/181121#M21496</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-02-02T10:26:59Z</dc:date>
    </item>
    <item>
      <title>Re: Passing parameters to macros and effectivity</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Passing-parameters-to-macros-and-effectivity/m-p/181122#M21497</link>
      <description>I'm afraid this should be tested to get a definite answer:(&lt;BR /&gt;
&lt;BR /&gt;
According to the macro calling logic in ArchiCAD, the size of the arrays should matter much less than the amount of parameters and the order of parameters. Passing each parameter does a name based search for the actual parameter in the parameter list of the called macro and a copy of values. This search used to be a relevant factor in macro calling speed in ArchiCAD. This search has been improved for AC13 a lot but having less parameters will make things faster - that's for sure.&lt;BR /&gt;
&lt;BR /&gt;
In general, I think having fewer but bigger arrays is better if the overall size is the same.&lt;BR /&gt;
&lt;BR /&gt;
HTH,</description>
      <pubDate>Tue, 02 Feb 2010 18:12:11 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Passing-parameters-to-macros-and-effectivity/m-p/181122#M21497</guid>
      <dc:creator>ztaskai</dc:creator>
      <dc:date>2010-02-02T18:12:11Z</dc:date>
    </item>
    <item>
      <title>Re: Passing parameters to macros and effectivity</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Passing-parameters-to-macros-and-effectivity/m-p/181123#M21498</link>
      <description>Thanks Zsolt for the clear and honest answer!&lt;BR /&gt;
If i get it right then I can conclude that:&lt;BR /&gt;
1- bigger arrays are no big deal&lt;BR /&gt;
2-using the old CALL method giving parameters by order rather than by name can make things faster&lt;BR /&gt;
That's good to know!&lt;BR /&gt;
I'll try to adapt my script to this,&lt;BR /&gt;
kind regards,&lt;BR /&gt;
olivier</description>
      <pubDate>Tue, 02 Feb 2010 21:46:49 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Passing-parameters-to-macros-and-effectivity/m-p/181123#M21498</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2010-02-02T21:46:49Z</dc:date>
    </item>
    <item>
      <title>Re: Passing parameters to macros and effectivity</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Passing-parameters-to-macros-and-effectivity/m-p/181124#M21499</link>
      <description>1 - Basically, yes.&lt;BR /&gt;
2 - I prefer the macro call syntax with named parameters since you lose track very soon with many parameters the other way - not to mention the case of intentionally omitting parameters. I just suggest you to keep the named parameters in the order of the definition to speed up the pairing up.&lt;BR /&gt;
&lt;BR /&gt;
Regards,</description>
      <pubDate>Thu, 04 Feb 2010 14:18:10 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Passing-parameters-to-macros-and-effectivity/m-p/181124#M21499</guid>
      <dc:creator>ztaskai</dc:creator>
      <dc:date>2010-02-04T14:18:10Z</dc:date>
    </item>
  </channel>
</rss>

