# FXRuby and Ruby 1.9 **URL:** \ **Category:** Ruby\ **Created:** [February 18, 2010, 2:04pm UTC](https://www.ruby-forum.com/t/fxruby-and-ruby-1-9/183665 "2010-02-18T14:04:38Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![alexd](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/96bed5/32.png) [@alexd](https://www.ruby-forum.com/u/alexd)\ **Post date:** [February 18, 2010, 2:04pm UTC](https://www.ruby-forum.com/t/fxruby-and-ruby-1-9/183665/1 "2010-02-18T14:04:38Z")
Forgive the post to this forum. The FXRuby forum doesn’t seem to be very active. I’m running a script to open a file dialog window. The script works fine in Ruby 1.8. In 1.9 the dialog box still opens and works, but I get a list of 44 error messages in the command window before it opens (the same two error messages repeated 22 times). The error messages are: FXCursor.cpp(281): FXASSERT(GetSystemMetrics(SM\_CXCURSOR)==32) failed. FXCursor.cpp(282): FXASSERT(GetSystemMetrics(SM\_CYCURSOR)==32) failed. Any ideas why this may be happening? I’m on a Windows 7 Professional, 64-bit OS. –Alex ---
**Author:** ![alexd](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/96bed5/32.png) [@alexd](https://www.ruby-forum.com/u/alexd)\ **Post date:** [February 18, 2010, 3:12pm UTC](https://www.ruby-forum.com/t/fxruby-and-ruby-1-9/183665/2 "2010-02-18T15:12:18Z")
On Thu, Feb 18, 2010 at 7:04 AM, Alex DeCaria [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > Forgive the post to this forum. The FXRuby forum doesn’t seem to be > very active. Not sure what forum you’re talking about, but as noted on the FXRuby home page, we have a mailing list for questions like these: ``` http://www.fxruby.org/community.html ``` I’m pretty sure you didn’t post there (or maybe I just missed this question). > 64-bit OS. > I’ve already seen your follow-up e-mail, but yes, it appears to be a > difference between 32-bit and 64-bit Windows. This may be something > that can be fixed in the FOX library; it’s not really anything that > can be addressed in the FXRuby layer. Hope this helps, Lyle ---
**Author:** ![alexd](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/96bed5/32.png) [@alexd](https://www.ruby-forum.com/u/alexd)\ **Post date:** [February 18, 2010, 2:07pm UTC](https://www.ruby-forum.com/t/fxruby-and-ruby-1-9/183665/3 "2010-02-18T14:07:10Z")
Alex DeCaria wrote: > Forgive the post to this forum. The FXRuby forum doesn’t seem to be > very active. > > I’m running a script to open a file dialog window. The script works > fine in Ruby 1.8. In 1.9 the dialog box still opens and works, but I > get a list of 44 error messages in the command window before it opens > (the same two error messages repeated 22 times). The error messages > are: > > FXCursor.cpp(281): FXASSERT(GetSystemMetrics(SM\_CXCURSOR)==32) failed. > FXCursor.cpp(282): FXASSERT(GetSystemMetrics(SM\_CYCURSOR)==32) failed. > > Any ideas why this may be happening? I’m on a Windows 7 Professional, > 64-bit OS. > > –Alex It does appear to be related to the OS, since the same script works fine with Ruby 1.9 on my XP Professional 32-bit system. –Alex ---
**Author:** ![alexd](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/96bed5/32.png) [@alexd](https://www.ruby-forum.com/u/alexd)\ **Post date:** [February 18, 2010, 3:24pm UTC](https://www.ruby-forum.com/t/fxruby-and-ruby-1-9/183665/4 "2010-02-18T15:24:47Z")
Lyle J. wrote: > On Thu, Feb 18, 2010 at 7:04 AM, Alex DeCaria > [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > > > Forgive the post to this forum. �The FXRuby forum doesn’t seem to be > > very active. > > Not sure what forum you’re talking about, but as noted on the FXRuby > home page, we have a mailing list for questions like these: > > ``` > http://www.fxruby.org/community.html > > ``` > > I’m pretty sure you didn’t post there (or maybe I just missed this > question). > > > 64-bit OS. > > I’ve already seen your follow-up e-mail, but yes, it appears to be a > > difference between 32-bit and 64-bit Windows. This may be something > > that can be fixed in the FOX library; it’s not really anything that > > can be addressed in the FXRuby layer. > > Hope this helps, > > Lyle Thanks Lyle - I was talking about the FXRuby Forum list on this site [http://www.ruby-forum.com/forum/35](http://www.ruby-forum.com/forum/35). I had posted a question there a week or so ago with no hits (doesn’t look like there is much traffic there anyway). I solved that one anyway. I didn’t know about the [www.fxruby.org](http://www.fxruby.org) forum. I’ll make more use of that in the future. I’m trying to get away from Tk and use more FXRuby. Thanks also for the reply. I can live with the error messages as long as it works correctly, which it seems to. May I ask an additional question? Is there a away when using an FXDirDialog to have the directory that is set with the dialog.directory command automatically expand the directory so you can see the subdirectories?. My dialog puts the target directory at the bottom of the dialog box, and then I have to click to expand it, and then scroll to see the contents. It would be nice if it was expanded automatically, and placed near the top of the box so you don’t have to do the extra click and scroll. –Alex ---
**Author:** ![alexd](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/96bed5/32.png) [@alexd](https://www.ruby-forum.com/u/alexd)\ **Post date:** [March 1, 2010, 1:32am UTC](https://www.ruby-forum.com/t/fxruby-and-ruby-1-9/183665/5 "2010-03-01T01:32:53Z")
Lyle, I’m still getting strange errors and segmentation faults on my 64-bit Windows OS with FXRuby apps that work just fine on a 32-bit OS. I see that over the past year or two the Fox Library has implemented certain fixes relevant to the 64-bit Windows architecture. I have two questions: 1. How often is FXRuby and the Fox libraries it uses updated? Have all the recent FOX Library changes been made in FXRuby? 2. Is mine an isolated case? Have you heard of others having issues with 64-bit Windows? I really like FXRuby, but I’m worried about pursuing it further if it isn’t going to be reliable on the newer architectures. –Alex