Lyle... Don''t forget that crash I''m seeing. Not trying to rush you, as I know fxruby is a labor of love and quite unpaid... Just want to make sure it''s on your list somewhere. :) Cheers, Hal
On Dec 9, 2004, at 8:47 PM, Hal Fulton wrote:> Don''t forget that crash I''m seeing...OK, a preliminary question... I''ve downloaded the tycho-0.0.7 release from RubyForge and see that the very first line of the main program (tycho.rb) is: require ''fox'' which is going to try to load your FXRuby 1.0 installation, not an FXRuby 1.2 installation. Is that what you intended? If not, and you''re trying to "port" Tycho to the FXRuby 1.2 API, the first step is going to be to change that to: require ''fox12'' but then there will be a number of other changes (i.e. to reflect the API changes between FXRuby 1.0 and FXRuby 1.2). That is to say, programs written for FXRuby 1.2 are not backwards-compatible with those written for FXRuby 1.2.
Lyle Johnson wrote:> which is going to try to load your FXRuby 1.0 installation, not an > FXRuby 1.2 installation. Is that what you intended? If not, and you''re > trying to "port" Tycho to the FXRuby 1.2 API, the first step is going to > be to change that to: > > require ''fox12''OK, in my own code, I did change that. It''s just not changed on rubyforge.> but then there will be a number of other changes (i.e. to reflect the > API changes between FXRuby 1.0 and FXRuby 1.2). That is to say, programs > written for FXRuby 1.2 are not backwards-compatible with those written > for FXRuby 1.2.Obviously I need to RTFM, because I didn''t know there was a backwards- compatibility issue. However, even so, doesn''t it fail awfully quickly?? On the create of the main window? I''ll do some reading... Thanks, Hal
On Dec 10, 2004, at 11:45 PM, Hal Fulton wrote:> Obviously I need to RTFM, because I didn''t know there was a backwards- > compatibility issue.Take a look at the release notes for the very first release (which was numbered 1.2a1), found here: http://www.fxruby.org/1.2/doc/changes.html and there''s a link to a "What''s New" document that covers most of the changes between FOX 1.0 and 1.2.> However, even so, doesn''t it fail awfully quickly?? On the create of > the main window?Well, keep in mind that when you call create() on the main window it recursively works its way down through all of the main window''s child windows, and their child windows, and so on, calling create(). So it''s not (necessarily) something wrong the main window itself, but perhaps one of the widgets it contains.> I''ll do some reading...OK.
Lyle, I just wanted to take advantage of Hal''s mail to report that since I have migrated FreeRIDE to FOX/FXRuby 1.2.x I, from time to time, experience SEGFAULT as well in the create of the FreeRIDE main window. I haven''t been able to track it down to the widget that is causing the problem, plus it happens only in some occasion... Shall I use gdb to trace the problem in the FOX code, any other advice to collect useful informationon to track the problem? Laurent -- Laurent JULLIARD http://www.moldus.org/~laurent
On Dec 12, 2004, at 12:16 PM, Laurent Julliard wrote:> Lyle, > > I just wanted to take advantage of Hal''s mail to report that since I > have migrated FreeRIDE to FOX/FXRuby 1.2.x I, from time to time, > experience SEGFAULT as well in the create of the FreeRIDE main window. > I haven''t been able to track it down to the widget that is causing the > problem, plus it happens only in some occasion... > > Shall I use gdb to trace the problem in the FOX code, any other advice > to collect useful informationon to track the problem?No, I imagine that using gdb is probably the most direct way to find out what''s causing the crash. Let me know what you find...