[fxruby-users] SEL_UPDATE not responsive

Michel Demazure michel at demazure.com
Wed Aug 18 05:24:34 EDT 2010

I know this phenomenon. You have to forbid threads. There is a fxruby
command for that. I forgot the exact syntax.

Michel  Demazure

michel at demazure.com


De : fxruby-users-bounces at rubyforge.org
[mailto:fxruby-users-bounces at rubyforge.org] De la part de Ralph Shnelvar
Envoyé : mercredi 18 août 2010 00:29
À : fxruby-users at rubyforge.org
Objet : [fxruby-users] SEL_UPDATE not responsive


I have read what I could about SEL_UPDATE and I understand that the block(s)
that get called "from" SEL_UPDATE only get called when "there is no more
work to do".



I took the splitter.rb example that comes with FXRuby. I put in a "puts" in
one of the SEL_UPDATE blocks and I get about 4 a second.   Not awful ... but
... why is it so slow?


In my code which is ... more or less ... similar to splitter.rb (just a lot
more widgets and buttons) and a single SEL_UPDATE block with almost nothing
in it ... and the block gets trigger once every four seconds rather than 4
times a second.  That's unacceptably slow.


How can I tell what's causing SEL _UPDATE to be so slow?  (CPU usage is at
4%.  I don't think I'm in a heavy loop.)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/fxruby-users/attachments/20100818/4e3a2605/attachment.html>

More information about the fxruby-users mailing list