Files | Admin

Notes:

Release Name: 3.3.1

Notes:
Building and Installing
* Please refer to the qtruby/README.build file

Highlights from the ChangeLog
* Fixed an occasional a crash on application exit
* Improved the resolution of the ruby classname to instantiate for an existing C++ instance, for DOM::Node subclasses and for KArchiveEntry subclasses.


Changes: 2004-10-11 Richard Dale <Richard_Dale@tipitina.demon.co.uk> * Set global flag 'application_terminated' when KDE::Application or KDE::UniqueApplication has returned from exec(). Once this is set the QtRuby runtime will no longer delete any C++ instances. This will hopefully fix crash on application exit problems reported by Thibauld Favre. CCMAIL: kde-bindings@kde.org 2004-10-08 Richard Dale <Richard_Dale@tipitina.demon.co.uk> * Reverted recent fix for crash on exit, as it only occured with a Qt::Application and seems to introduce a crash in KDE apps where none existed before. CCMAIL: kde-bindings@kde.org CCMAIL: thibauld.favre@laposte.net 2004-10-06 Richard Dale <Richard_Dale@tipitina.demon.co.uk> * When a Korundum application exits, the top level widgets are now destroyed as well as the KDE::Application itself. This fixes a problem where the ruby garbage collection frees instances in an arbitrary order afer the program has exited, and destroys a Hash containing QMetaData info needed for tidying up. 2004-10-04 Richard Dale <Richard_Dale@tipitina.demon.co.uk> * When a ruby app exits, rb_gc_call_finalizer_at_exit() is called and all the ruby instances are garbage collected. The problem is that this is done in an arbitrary order, and KDE::Application was occasionally crashing in its destructor because QMetaObject info it still needed was being deleted before then. * Fixes problem reported by Thibauld Favre CCMAIL: <tfavre@mandrakesoft.com> 2004-10-03 Richard Dale <Richard_Dale@tipitina.demon.co.uk> * Removed warning about '*' being used as an argument prefix 2004-09-30 Richard Dale <Richard_Dale@tipitina.demon.co.uk> * Added some rtti tests for DOM::Node to instantiate a more accurate ruby class 2004-09-30 Richard Dale <Richard_Dale@tipitina.demon.co.uk> * The resolve_classname() function in qtruby handlers.cpp uses the various Qt rtti mechanisms to get a more accurate classname to instantiate as a ruby instance. It has now been extended with a callback to the Korundum library to do the same for KDE classes. * This fixes a problem reported by Zack Rusin where a KArchiveEntry returned to ruby was not being correctly constructed as either a KArchiveDirectory or KArchiveFile according to the KArchiveEntry::isDirectory() method CCMAIL: zack@kde.org