changes.xml

<?xml version="1.0" encoding="UTF-8"?>
<chapter id="changes">
  <title>Change History</title>

  <simplesect>
    <title>Changes For Version 1.6.19 (February 28, 2009)</title>

    <itemizedlist mark="bullet">
      <listitem>
        <para>The previous release of FXRuby couldn't be built from source against Ruby 1.9.1 final
        due to a change in some of the file-related utility libraries
        (see <ulink
        url="http://rubyforge.org/tracker/index.php?func=detail&amp;aid=23786&amp;group_id=300&amp;atid=1223">RubyForge
        Bug #23786</ulink>). This problem has been corrected.</para>
      </listitem>
      <listitem>
        <para>The previous release of FXRuby couldn't be built from source against Ruby versions 1.8.5 or
        earlier (see <ulink
        url="http://rubyforge.org/tracker/index.php?func=detail&amp;aid=23967&amp;group_id=300&amp;atid=1223">RubyForge
        Bug #23967</ulink>). This problem has been corrected.</para>
      </listitem>
      <listitem>
        <para>The <methodname>addAccel</methodname> method for the <classname>FXAccelTable</classname> class
        now accepts lambda functions (or any other objects that respond to <methodname>call</methodname>). See
        the <ulink url="http://www.fxruby.org/doc/api/classes/Fox/FXAccelTable.html">API documentation</ulink>
        for <classname>FXAccelTable</classname> for examples of how this works.</para>
      </listitem>
    </itemizedlist>
  </simplesect>

  <simplesect>
    <title>Changes For Version 1.6.18 (December 29, 2008)</title>

    <itemizedlist mark="bullet">
      <listitem>
        <para>Some users were having trouble building FXRuby on 64-bit operating systems
        (see <ulink
        url="http://rubyforge.org/tracker/index.php?func=detail&amp;aid=23375&amp;group_id=300&amp;atid=1223">RubyForge
        Bug #23375</ulink>). This problem has been corrected.</para>
      </listitem>
    </itemizedlist>
  </simplesect>

  <simplesect>
    <title>Changes For Version 1.6.17 (December 24, 2008)</title>

    <itemizedlist mark="bullet">
      <listitem>
        <para>The Ruby interpreter was generating a large number of warning messages about redefined methods
        in the <filename>kwargs.rb</filename> library
        (see <ulink
        url="http://rubyforge.org/tracker/index.php?func=detail&amp;aid=19231&amp;group_id=300&amp;atid=1223">RubyForge
        Bug #19231</ulink> and elsewhere). This problem has been corrected.</para>
      </listitem>

      <listitem>
        Due to recent changes in Ruby's garbage collection algorithm, FXRuby applications could under some circumstances
        crash for large numbers of table items
        (see RubyForge bugs <ulink url="http://rubyforge.org/tracker/index.php?func=detail&amp;aid=21983&amp;group_id=300&amp;atid=1223">21983</ulink> and <ulink url="http://rubyforge.org/tracker/index.php?func=detail&amp;aid=23188&amp;group_id=300&amp;atid=1223">23188</ulink>).
        This bug has been fixed.
      </listitem>
      
      <listitem>
        <para>The documentation for the <classname>FXTable</classname> class referred to the non-existent <methodname>setColumnX</methodname>
        and <methodname>setRowY</methodname> instance methods
        (see <ulink
        url="http://rubyforge.org/tracker/index.php?func=detail&amp;aid=21987&amp;group_id=300&amp;atid=1223">RubyForge
        Bug #21987</ulink>). These entries have been removed from the documentation.</para>
      </listitem>

      <listitem>
        <para>A number of instance methods for the <classname>FXTable</classname> class could crash an application if they
        were passed out-of-bounds index arguments
        (see <ulink
        url="http://rubyforge.org/tracker/index.php?func=detail&amp;aid=21987&amp;group_id=300&amp;atid=1223">RubyForge
        Bug #21987</ulink>). These methods now raise <classname>IndexError</classname> when they're passed out-of-bounds
        indexes.</para>
      </listitem>

      <listitem>
        <para>Due to a change in the URL scheme for the Dilbert web site, the <filename>dilbert.rb</filename> example
        program was no longer working properly
        (see <ulink
        url="http://rubyforge.org/tracker/index.php?func=detail&amp;aid=21538&amp;group_id=300&amp;atid=1223">RubyForge
        Bug #21538</ulink>). This has been fixed.</para>
      </listitem>

      <listitem>
        <para>The <methodname>lower</methodname> method for the <classname>FXRangef</classname> was returning
        <constant>self</constant> instead of an <classname>FXVec3f</classname> instance for the range's low
        bound
        (see <ulink
        url="http://rubyforge.org/tracker/index.php?func=detail&amp;aid=22488&amp;group_id=300&amp;atid=1223">RubyForge
        Bug #22488</ulink>). This has been fixed.</para>
      </listitem>

      <listitem>
        <para>Made a number of minor fixes for compatibility with Ruby 1.9.1.</para>
      </listitem>
    </itemizedlist>
  </simplesect>

  <simplesect>
    <title>Changes For Version 1.6.16 (July 3, 2008)</title>

    <itemizedlist mark="bullet">
      <listitem>
        <para>Historically, if you called <methodname>create</methodname> on a
        window before its parent window was created, your application would
        crash (see <ulink
        url="http://rubyforge.org/tracker/index.php?func=detail&amp;aid=20702&amp;group_id=300&amp;atid=1223">RubyForge
        Bug #20702</ulink> and elsewhere). Now, the code should raise a
        <constant>RuntimeError</constant> with a message indicating the
        problem.</para>
      </listitem>

      <listitem>
        <para>The message data that the <classname>FXPicker</classname> widget
        sends along with its <constant>SEL_CHANGED</constant> and
        <constant>SEL_COMMAND</constant> messages wasn't being handled
        properly, and as a result, applications using this widget could crash
        (see <ulink
        url="http://rubyforge.org/tracker/index.php?func=detail&amp;aid=20780&amp;group_id=300&amp;atid=1223">RubyForge
        Bug #20780</ulink>). This problem has been fixed.</para>
      </listitem>
    </itemizedlist>
  </simplesect>

  <simplesect>
    <title>Changes For Version 1.6.15 (June 4, 2008)</title>

    <itemizedlist mark="bullet">
      <listitem>
        <para>FXRuby applications could crash (with a segmentation fault) if
        <constant>nil</constant> was passed in as the first argument to
        <methodname>FXDialogBox.new</methodname> or
        <methodname>FXMainWindow.new</methodname> (see <ulink
        url="http://rubyforge.org/tracker/index.php?func=detail&amp;aid=14642&amp;group_id=300&amp;atid=1223">RubyForge
        Bug #14642</ulink>). These methods now raise an
        <constant>ArgumentError</constant> if <constant>nil</constant> is
        passed as the first argument.</para>
      </listitem>

      <listitem>
        <para>You should only ever construct one <classname>FXApp</classname>
        object per application, but there was no protection against doing so
        in the code (see <ulink
        url="http://rubyforge.org/tracker/index.php?func=detail&amp;aid=16275&amp;group_id=300&amp;atid=1223">RubyForge
        Bug #16275</ulink>). Now, <methodname>FXApp.new</methodname> will
        raise a <classname>RuntimeException</classname> if an
        <classname>FXApp</classname> object already exists.</para>
      </listitem>

      <listitem>
        <para>The <filename>babelfish.rb</filename> example program, which
        previously depended on an external web service to perform translation
        between languages, was broken since that web service no longer exists
        (see <ulink
        url="http://rubyforge.org/tracker/index.php?func=detail&amp;aid=16962&amp;group_id=300&amp;atid=1223">RubyForge
        Bug #16962</ulink>). The example has now been updated to use Dr. Nic's
        <ulink url="http://tranexp.rubyforge.org/">Tranexp</ulink> library
        instead.</para>
      </listitem>

      <listitem>
        <para>The value of the <constant>MBOX_SAVE_CANCEL_DONTSAVE</constant>
        option (for the <classname>FXMessageBox</classname> class) wasn't
        wrapped properly and was unusable (see <ulink
        url="http://rubyforge.org/tracker/index.php?func=detail&amp;aid=17094&amp;group_id=300&amp;atid=1223">RubyForge
        Bug #17094</ulink>). There was also no constant corresponding to the
        <constant>MBOX_CLICKED_DONTSAVE</constant> return value. Both of these
        problems have been fixed.</para>
      </listitem>

      <listitem>
        <para>The fields for new <classname>FXHiliteStyle</classname> objects
        were uninitialized and as a result sometimes gave unpredictable
        results (see <ulink
        url="http://rubyforge.org/tracker/index.php?func=detail&amp;aid=19637&amp;group_id=300&amp;atid=1223">RubyForge
        Bug #19637</ulink>). This has been fixed.</para>
      </listitem>

      <listitem>
        <para>The <methodname>columnHeaderFont</methodname> and
        <methodname>rowHeaderFont</methodname> attributes for
        <classname>FXTable</classname> weren't implemented properly (see
        <ulink
        url="http://rubyforge.org/tracker/index.php?func=detail&amp;aid=20142&amp;group_id=300&amp;atid=1223">RubyForge
        Bug #20142</ulink>). This has been fixed.</para>
      </listitem>

      <listitem>
        <para>Ruby 1.8.7 adds a new <methodname>first</methodname> method to
        the <classname>Enumerable</classname> module, and this conflicts with
        the existing <methodname>first</methodname> method defined in the
        <classname>FXWindow</classname> base class for a number of FXRuby
        classes which mix in <classname>Enumerable</classname> (see <ulink
        url="http://rubyforge.org/tracker/index.php?func=detail&amp;aid=20418&amp;group_id=300&amp;atid=1223">RubyForge
        Bug #20418</ulink>). This problem has been resolved.</para>
      </listitem>