All,
At long last, FXRuby version 1.4.1 is available for download from this
page:
http://rubyforge.org/frs/?group_id=300&release_id=2719
Since this is the first release in this series (i.e. compatible with
FOX 1.4), it should be considered unstable. Please report any problems
either to the mailing list, or even better, log them in the Bug Tracker
at RubyForge, here:
http://rubyforge.org/tracker/?atid=1223&group_id=300&func=browse
As usual, the code is provided as a Win32 installer or a binary Gem
(both compatible with the latest One-Click Installer for Ruby 1.8.2),
as a source gem, and as a source tarball. For instructions on compiling
FXRuby from source, please see:
http://www.fxruby.org/doc/build.html
For a summary of the changes in this release, please see this page:
http://www.fxruby.org/doc/changes.html
As always, the FXRuby home page is here:
http://www.fxruby.org
Enjoy,
Lyle
Yay! *Round of applause for Lyle* Saturday, August 20, 2005, 8:36:32 AM, you wrote:> All,> At long last, FXRuby version 1.4.1 is available for download from this > page:> http://rubyforge.org/frs/?group_id=300&release_id=2719> Since this is the first release in this series (i.e. compatible with > FOX 1.4), it should be considered unstable. Please report any problems > either to the mailing list, or even better, log them in the Bug Tracker > at RubyForge, here:> > http://rubyforge.org/tracker/?atid=1223&group_id=300&func=browse> As usual, the code is provided as a Win32 installer or a binary Gem > (both compatible with the latest One-Click Installer for Ruby 1.8.2), > as a source gem, and as a source tarball. For instructions on compiling > FXRuby from source, please see:> http://www.fxruby.org/doc/build.html> For a summary of the changes in this release, please see this page:> http://www.fxruby.org/doc/changes.html> As always, the FXRuby home page is here:> http://www.fxruby.org> Enjoy,> LyleSee ya, -- _/ _/ _/ Jacob Hanson _/ _/_/_/ mailto:jacdx@jacobhanson.com _/_/_/ _/ _/ http://www.jacobhanson.com
On 8/20/05, Lyle Johnson <lyle@knology.net> wrote:> All, > > At long last, FXRuby version 1.4.1 is available for download > > Enjoy, > > LyleThanks for your hard work Lyle. -Rich
w00t! Lyle, did you ever get that steak diner we promised to you? Sander On Saturday 20 August 2005 11:44 am, Jacob Hanson wrote:> Yay! *Round of applause for Lyle* > > Saturday, August 20, 2005, 8:36:32 AM, you wrote: > > All, > > > > At long last, FXRuby version 1.4.1 is available for download from this > > page: > > > > http://rubyforge.org/frs/?group_id=300&release_id=2719 > > > > Since this is the first release in this series (i.e. compatible with > > FOX 1.4), it should be considered unstable. Please report any problems > > either to the mailing list, or even better, log them in the Bug Tracker > > at RubyForge, here: > > > > > > http://rubyforge.org/tracker/?atid=1223&group_id=300&func=browse > > > > As usual, the code is provided as a Win32 installer or a binary Gem > > (both compatible with the latest One-Click Installer for Ruby 1.8.2), > > as a source gem, and as a source tarball. For instructions on compiling > > FXRuby from source, please see: > > > > http://www.fxruby.org/doc/build.html > > > > For a summary of the changes in this release, please see this page: > > > > http://www.fxruby.org/doc/changes.html > > > > As always, the FXRuby home page is here: > > > > http://www.fxruby.org > > > > Enjoy, > > > > Lyle > > See ya, > -- > _/ _/ _/ Jacob Hanson > _/ _/_/_/ mailto:jacdx@jacobhanson.com > _/_/_/ _/ _/ http://www.jacobhanson.com > > _______________________________________________ > fxruby-users mailing list > fxruby-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/fxruby-users
> Since this is the first release in this series (i.e. compatible with > FOX 1.4), it should be considered unstable. Please report any problems > either to the mailing list, or even better, log them in the Bug Tracker > at RubyForge, here:------------------------------------------------ Bug 1 Code like: @@cursor_w = FXGIFCursor.new(@window.getApp, pix) FXFileStream.open(''icons/room_w.gif'', FXStreamLoad) { |stream| @@cursor_w.loadPixels(stream) } @@cursor_w.create Results in: ./lib/IFMapper/FXMap.rb:1222:in `loadPixels'': undefined method `setPosition'' for #<Fox::FXFileStream:0x72c0f40> -------------------- Bug 2 uninitialized constant Fox::FXWindow::ID_QUERY_TIP -------------------- Bug 3 Tons of crashes (segfaults) on calling GC.start and on trying to initialize canvas. Best way to test this is to download the latest IFMapper from rubyforge.
On Aug 20, 2005, at 9:08 PM, Gonzalo Garramuno wrote:> ------------------------------------------------ Bug 1 > Code like: > @@cursor_w = FXGIFCursor.new(@window.getApp, pix) > FXFileStream.open(''icons/room_w.gif'', FXStreamLoad) { |stream| > @@cursor_w.loadPixels(stream) > } > @@cursor_w.create > > Results in: > ./lib/IFMapper/FXMap.rb:1222:in `loadPixels'': undefined method > `setPosition'' > for #<Fox::FXFileStream:0x72c0f40>OK, this has been fixed for version 1.4.2.> -------------------- Bug 2 > uninitialized constant Fox::FXWindow::ID_QUERY_TIPThe ID_QUERY_TIP and ID_QUERY_HELP message identifiers were removed in FOX 1.3.4 and replaced with the SEL_QUERY_TIP and SEL_QUERY_HELP message types. In your code, you''d want to replace this bit: @canvas.connect(SEL_UPDATE, method(:update_cb)) with this: @canvas.connect(SEL_QUERY_TIP, method(:update_cb)) and then your update_cb() method would look something like this: def update_cb(sender, sel, ptr) sender.text = "The tooltip text" end> -------------------- Bug 3 > Tons of crashes (segfaults) on calling GC.start and on trying to > initialize > canvas.I''m not sure I understand how to reproduce this one. I''ve downloaded IFMapper, started it, clicked on the canvas in a few places to create rooms, then closed the canvas. Then created a new one and did it again, etc. Should it have crashed on me? Can you give me some specific set of steps that is likely to reproduce the problem? And which platform are you seeing the crashes on (Windows or Linux)?
Any experiences so far about what breaks going from 1.2->1.4? Did
anything change in the API?
A diff of the example dirs (1.2.6 vs 1.4.1) suggests that very little
has changed in the API, at least to the extent covered by the examples
(which would be pleasant news). It looks like new features _just_
_work_, such as editable table cells in table.rb.
That''s very cool. Lyle and Jeroen, thanks!
--
vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407
On Aug 21, 2005, at 7:02 PM, Joel VanderWerf wrote:> Any experiences so far about what breaks going from 1.2->1.4? Did > anything change in the API?There were a handful of minor changes, but they were for the most part additions and not changes to existing APIs. A lot of the changes were things that matter at the C++ layer but not so much in the Ruby layer (e.g. a lot of functions'' return type changed from an FXString to a const FXString&, that sort of thing). One of the most significant changes to the existing architecture, as far as the public API''s concerned, was the stuff having to with floating toolbars (i.e. the new FXDockSite and FXDockBar base classes). Actually, I''m still trying to get a handle on those changes. ;)> A diff of the example dirs (1.2.6 vs 1.4.1) suggests that very little > has changed in the API, at least to the extent covered by the examples > (which would be pleasant news). It looks like new features _just_ > _work_, such as editable table cells in table.rb.Yes, I''ve had to make surprisingly few changes to the example programs and unit tests. Am still trying to get the image.rb and imageviewer.rb examples back up to speed, but expect to have that fixed in the next day or so.> That''s very cool. Lyle and Jeroen, thanks!Thanks, Joel. You know the drill, just shoot a bug report to the list or the tracker as time allows, if you run into anything.
Windows. With the new 1.4.2 release, it is better. However, it is still crashing on garbage collecting every so often. In this application, a forced garbage collection using GC.start often happens when the map window is closed. I can get it to crash consistently if I create a map, play a little and then close the window (a requester to save pops up, and I hit no).> > I''m not sure I understand how to reproduce this one. I''ve downloaded > IFMapper, started it, clicked on the canvas in a few places to create > rooms, then closed the canvas. Then created a new one and did it again, > etc. Should it have crashed on me? Can you give me some specific set of > steps that is likely to reproduce the problem? And which platform are > you seeing the crashes on (Windows or Linux)? >