From: Lyle Johnson <ljohnson@...>
Date: 2002-03-14T23:26:21+09:00
Subject: Re: [FXRuby] advanced questions and bug

> There's a standalone ruby file containing the subjects of all my questions
> Get it at: http://www.ugcs.caltech.edu/~leon/ruby/equipmentlist.rb
> It's supposed to work on multiple platforms. Works fine on Linux.

I haven't downloaded the program yet, I'm just going to try to hit these
questions first. After I take a look at the program I may send you a
follow-up e-mail about stuff.

> * FXList#sort doesn't sort. The <=> method is called on the FXListItem
>   objects, but the list doesn't display the sort. What's going on?

Umm, are you sure about that? The <=> method shouldn't be getting called for
the FXRuby release you have ;) Sorting of FXList (and other kinds of list
widgets) was broken in the FXRuby-0.99.189 release, but it's fixed for the
upcoming FXRuby-1.0.x release.

> * Running a thread in a Proc connected to SEL_COMMAND will crash Ruby
>   on windows. What causes the bug? (might be version related)

Threads work correctly on Linux and the Cygwin build of Ruby. They do not
work for the Visual C++ build of Ruby, using identical source code, which
means there's some subtle (or not so simple) implementation difference for
Ruby's threads that I'm going to have to debug. I've floated a few questions
about Ruby's threads implementation in the past and basically got the
impression that no one (other than maybe Matz himself) really knows how this
works, so this is probably going to be an uphill battle.

> * Is setDNDData usable?

Well, I think so. This sounds like a loaded question, the purpose of which
will become more evident once I see your code ;)

> * How does one get FXList to send SEL_MOTION? Must it be done manually?

For fox-0.99.189, Jeroen had commented out that line that forwards
SEL_MOTION messages to the window's target. For the fox-1.0.x release he's
turned that back on, i.e. FXList and other windows should be sending those
SEL_MOTION messages again.