<?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: values range crashes ArchiCAD if lower_limit &amp;gt; upper_limit in Libraries &amp; objects</title>
    <link>https://community.graphisoft.com/t5/Libraries-objects/values-range-crashes-ArchiCAD-if-lower-limit-gt-upper-limit/m-p/264222#M4227</link>
    <description>I will bring this to the attention of GRAPHISOFT's GDL developers.</description>
    <pubDate>Sun, 04 Feb 2018 17:18:07 GMT</pubDate>
    <dc:creator>Laszlo Nagy</dc:creator>
    <dc:date>2018-02-04T17:18:07Z</dc:date>
    <item>
      <title>values range crashes ArchiCAD if lower_limit &gt; upper_limit</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/values-range-crashes-ArchiCAD-if-lower-limit-gt-upper-limit/m-p/264221#M4226</link>
      <description>&lt;DIV class="actalk-migrated-content"&gt;&lt;R&gt;Hi,&lt;BR /&gt;
I've run into a problem that seems to be a serious bug. In AC18 (tested only in that) I added a 
&lt;PRE&gt;values range [-A/2 + xSomeCalculatedValue1, A/2 - xSomeCalculatedValue2]&lt;/PRE&gt;
statement to a parameter script of a window sash. The &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;xSomeCalculatedValue&lt;E&gt;&lt;/E&gt; local variables were some ordinary dimensions.&lt;BR /&gt;
But, since the default A (width) parameter set among the parameters of the sash macro, the lower limit happened to be higher than the upper value &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;(A&lt;E&gt;&lt;/E&gt; being smaller than &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;xSomeCalculatedValue1 + xSomeCalculatedValue2),&lt;E&gt;&lt;/E&gt; so the ArchiCAD crashed (didn't respond) . After restarts, since the stuff stayed there, all edit attempts were unsuccessful, so I would have throw the whole macro away for a small bug if I hadn't been able to convert it to XML and commenting the bad values line there and converting back to gdl. &lt;BR /&gt;
I knew the trick but most don't.&lt;BR /&gt;
&lt;BR /&gt;
The bug seemed to be a missing checking if &lt;I&gt;&lt;/I&gt;&lt;S&gt;&lt;I&gt;&lt;I&gt;&lt;/I&gt;&lt;/I&gt;&lt;/S&gt;lower_limit &amp;gt; upper_limit&lt;E&gt;&lt;/E&gt; in the interpreter.&lt;BR /&gt;
&lt;BR /&gt;
Note that I haven't tested it in newer versions, so the bug might be fixed.&lt;/R&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 24 May 2023 09:34:40 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/values-range-crashes-ArchiCAD-if-lower-limit-gt-upper-limit/m-p/264221#M4226</guid>
      <dc:creator>Sam Karli</dc:creator>
      <dc:date>2023-05-24T09:34:40Z</dc:date>
    </item>
    <item>
      <title>Re: values range crashes ArchiCAD if lower_limit &gt; upper_limit</title>
      <link>https://community.graphisoft.com/t5/Libraries-objects/values-range-crashes-ArchiCAD-if-lower-limit-gt-upper-limit/m-p/264222#M4227</link>
      <description>I will bring this to the attention of GRAPHISOFT's GDL developers.</description>
      <pubDate>Sun, 04 Feb 2018 17:18:07 GMT</pubDate>
      <guid>https://community.graphisoft.com/t5/Libraries-objects/values-range-crashes-ArchiCAD-if-lower-limit-gt-upper-limit/m-p/264222#M4227</guid>
      <dc:creator>Laszlo Nagy</dc:creator>
      <dc:date>2018-02-04T17:18:07Z</dc:date>
    </item>
  </channel>
</rss>

