search for: disablethreads

Hello all, Run groupbox.rb example in any of the two alpha versions and click the radiobutton in the upper right group box (those named Hilvesum 1, Hilversum 2, etc). You''ll notice that once a radiobutton is checked, it remains checked when some other radiobutton is checked. What''s the reason? Thank you. -- Best regards, Yuri Leikind

Hi Lyle, I have noticed a very small problem with the FXColorDialog class: when changing the color with the color wheel, it takes quite a long time (until 4 seconds, sometimes less) for the other panels of the dialog to synchronize. The opposite is also true: when changing the color with the sliders, it may take sometimes until 4 seconds for the color wheel to reflect the change.

I find that when a running fxruby program looses focus or another window is placed in front of it, when the fxruby window regains focus, many times the gui is now frozen or blank. This seems to happen especially frequently when the window covering it is a java or fox based application. Usually it comes back but sometimes it takes several minutes to do so. I would really like to find someway

...ere should be a little clock in the lower >right-hand corner that''s being updated by a thread, i.e. threads support is >"enabled" for that particular program. Hmm, that groupbox.rb code breaks "correctly" (doesn''t update time very often) when application.disableThreads is called. Do you mean an external thread that *directly* affects FXRuby components? Mine does not interface with FXRuby at all - it merely communicates via a synchonized queue and it is the FXRuby process (via a chore) that does the alteration. Perhaps that is it? *shrug* bil