<?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: Compatibility Changes in GDL in ARCHICAD 19 in Libraries &amp; objects</title>
    <link>https://community.graphisoft.com/t5/Libraries-objects/Compatibility-Changes-in-GDL-in-ARCHICAD-19/m-p/277816#M9741</link>
    <description>At least we have the heads up this time.</description>
    <pubDate>Tue, 23 Jun 2015 14:02:06 GMT</pubDate>
    <dc:creator>Erich</dc:creator>
    <dc:date>2015-06-23T14:02:06Z</dc:date>
    <item>
      <title>Compatibility Changes in GDL in ARCHICAD 19</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Compatibility-Changes-in-GDL-in-ARCHICAD-19/m-p/277813#M9738</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;R&gt;Dear All,&lt;BR /&gt;
&lt;BR /&gt;
Please be aware of changes between &lt;B&gt;ARCHICAD 18&lt;/B&gt; and &lt;B&gt;ARCHICAD 19&lt;/B&gt; in GDL script usage. Firstly objects will only be able to use the speed improvement provided by the new &lt;B&gt;Predictive Background Processing &lt;/B&gt;feature of &lt;B&gt;ARCHICAD 19 &lt;/B&gt;if they follow particular rules. Secondly we have removed the possibility of using User Globals for data transfer between objects. You can find a document at the &lt;A href="http://download.graphisoft.com/ftp/techsupport/downloads/GDL/GDL%20changes%20in%20ArchiCAD%2019%20v1.1.pdf" target="_blank"&gt;&lt;/A&gt;&lt;S&gt;&lt;A href="http://download.graphisoft.com/ftp/techsupport/downloads/GDL/GDL%20changes%20in%20ArchiCAD%2019%20v1.1.pdf" target="_blank"&gt;&lt;/A&gt;&lt;A href="&amp;lt;/s&amp;gt;&amp;lt;LINK_TEXT text=&amp;quot;http://download.graphisoft.com/ftp/tech ... 20v1.1.pdf&amp;quot;&amp;gt;http://download.graphisoft.com/ftp/techsupport/downloads/GDL/GDL%20changes%20in%20ArchiCAD%2019%20v1.1.pdf&amp;lt;/LINK_TEXT&amp;gt;&amp;lt;e&amp;gt;"&gt;&lt;/A&gt;&lt;/S&gt;&lt;LINK_TEXT text="http://download.graphisoft.com/ftp/tech ... 20v1.1.pdf"&gt;http://download.graphisoft.com/ftp/techsupport/downloads/GDL/GDL%20changes%20in%20ArchiCAD%2019%20v1.1.pdf&lt;/LINK_TEXT&gt;&lt;E&gt;&lt;/E&gt; address describing these changes in detail. The document also contains information on a restriction in GDL usage that is planned to be introduced in ARCHICAD 20. &lt;BR /&gt;
&lt;BR /&gt;
Best regards&lt;/R&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 19 Jun 2015 13:13:23 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Compatibility-Changes-in-GDL-in-ARCHICAD-19/m-p/277813#M9738</guid>
      <dc:creator>AndorSzoke</dc:creator>
      <dc:date>2015-06-19T13:13:23Z</dc:date>
    </item>
    <item>
      <title>Re: Compatibility Changes in GDL in ARCHICAD 19</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Compatibility-Changes-in-GDL-in-ARCHICAD-19/m-p/277814#M9739</link>
      <description>I don't think most users will realise the implications of these changes until they start to use 19 and find their objects may not be working as they once did.&lt;BR /&gt;
In fact most users will not realise until version 20 when most of these changes will come into effect.&lt;BR /&gt;
&lt;BR /&gt;
GDL developers will get error messages while scripting in 19 that the end user will not see at all (and objects should work as they have done in the past until version 20 comes along).&lt;BR /&gt;
&lt;BR /&gt;
So GDL developers it is time to start checking your scripting.&lt;BR /&gt;
&lt;BR /&gt;
Barry.</description>
      <pubDate>Tue, 23 Jun 2015 04:18:25 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Compatibility-Changes-in-GDL-in-ARCHICAD-19/m-p/277814#M9739</guid>
      <dc:creator>Barry Kelly</dc:creator>
      <dc:date>2015-06-23T04:18:25Z</dc:date>
    </item>
    <item>
      <title>Re: Compatibility Changes in GDL in ARCHICAD 19</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Compatibility-Changes-in-GDL-in-ARCHICAD-19/m-p/277815#M9740</link>
      <description>Ouch, I will have to start testing our large library of product object-libraries we've collected over the years, to see if they are compatible and to see if there are updates.  &lt;IMG src="https://community.graphisoft.com/legacyfs/online/emojis/icon_sad.gif" style="display : inline;" /&gt;</description>
      <pubDate>Tue, 23 Jun 2015 08:01:00 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Compatibility-Changes-in-GDL-in-ARCHICAD-19/m-p/277815#M9740</guid>
      <dc:creator>Erwin Edel</dc:creator>
      <dc:date>2015-06-23T08:01:00Z</dc:date>
    </item>
    <item>
      <title>Re: Compatibility Changes in GDL in ARCHICAD 19</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Compatibility-Changes-in-GDL-in-ARCHICAD-19/m-p/277816#M9741</link>
      <description>At least we have the heads up this time.</description>
      <pubDate>Tue, 23 Jun 2015 14:02:06 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Compatibility-Changes-in-GDL-in-ARCHICAD-19/m-p/277816#M9741</guid>
      <dc:creator>Erich</dc:creator>
      <dc:date>2015-06-23T14:02:06Z</dc:date>
    </item>
    <item>
      <title>Re: Compatibility Changes in GDL in ARCHICAD 19</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Compatibility-Changes-in-GDL-in-ARCHICAD-19/m-p/277817#M9742</link>
      <description>&lt;BLOCKQUOTE&gt;Barry wrote:&lt;BR /&gt;I don't think most users will realise the implications of these changes until they start to use 19 and find their objects may not be working as they once did.&lt;BR /&gt;
In fact most users will not realise until version 20 when most of these changes will come into effect.&lt;BR /&gt;
&lt;BR /&gt;
GDL developers will get error messages while scripting in 19 that the end user will not see at all (and objects should work as they have done in the past until version 20 comes along).&lt;BR /&gt;
&lt;BR /&gt;
So GDL developers it is time to start checking your scripting.&lt;BR /&gt;
&lt;BR /&gt;
Barry.&lt;/BLOCKQUOTE&gt;

We use a zone stamp that lets our users select surfaces as parameters to be used in a room finish schedule. The name of the surfaces are requested in the parameter script and then parsed to extract a text designation found in the name that will be displayed on the room finish schedule.  We really liked the ease of use.   Sounds like we will lose the parsing capability in v20.  Wish I knew a way to keep it.</description>
      <pubDate>Tue, 30 Jun 2015 21:56:50 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Compatibility-Changes-in-GDL-in-ARCHICAD-19/m-p/277817#M9742</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2015-06-30T21:56:50Z</dc:date>
    </item>
    <item>
      <title>Re: Compatibility Changes in GDL in ARCHICAD 19</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Compatibility-Changes-in-GDL-in-ARCHICAD-19/m-p/277818#M9743</link>
      <description>From my reading of the "GDL changes in ArchiCAD 19 v1.1" document, you just can't have the request in the parameter script. It looks like moving it to another scripting environment will allow the requests to continue functioning.</description>
      <pubDate>Tue, 30 Jun 2015 22:36:05 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Compatibility-Changes-in-GDL-in-ARCHICAD-19/m-p/277818#M9743</guid>
      <dc:creator>Erich</dc:creator>
      <dc:date>2015-06-30T22:36:05Z</dc:date>
    </item>
    <item>
      <title>Re: Compatibility Changes in GDL in ARCHICAD 19</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/Compatibility-Changes-in-GDL-in-ARCHICAD-19/m-p/277819#M9744</link>
      <description>&lt;BLOCKQUOTE&gt;Erich wrote:&lt;BR /&gt;From my reading of the "GDL changes in ArchiCAD 19 v1.1" document, you just can't have the request in the parameter script. It looks like moving it to another scripting environment will allow the requests to continue functioning.&lt;/BLOCKQUOTE&gt;

Sure you can use the REQUEST commands in the 2D and 3D scripts and they will work perfectly.&lt;BR /&gt;
Problem is as far as I know you can't set a parameter value from a 2D or 3D script so you won't be able to use that parameter in a schedule.&lt;BR /&gt;
&lt;BR /&gt;
Barry.</description>
      <pubDate>Wed, 01 Jul 2015 03:37:03 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/Compatibility-Changes-in-GDL-in-ARCHICAD-19/m-p/277819#M9744</guid>
      <dc:creator>Barry Kelly</dc:creator>
      <dc:date>2015-07-01T03:37:03Z</dc:date>
    </item>
  </channel>
</rss>

