wxruby development - Jul 2007 - [ wxruby-Bugs-12015 ] incorrect behaviour on threads

Bugs item #12015, was opened at 2007-07-05 13:21
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=218&aid=12015&group_id=35

Category: Incorrect behavior
Group: current
Status: Open
Resolution: None
Priority: 3
Submitted By: Reinier Voost (rvoost)
Assigned to: Kevin Smith (qualitycode)
Summary: incorrect behaviour on threads

Initial Comment:
I have created an application with WXRuby which looks great. 
Though my application also uses threads.
The issue I have now, is that my threads only work when I am showing activity on
the screen (like clicking, or even just moving my mouse over the panel).
Though when I am not active, the threads are also not active.

After some investigation I found out (or I guess) that the method main_loop is a
thread on its own dominating all others.
I tried to prioritize my threads higher then the thread of main_loop but without
any positive result.

I can enforce my thread to execute (as it is set to sleep immediately) by using
the .run command, though for some unclear thing it only runs once and is put on
sleep again.
So to conclude:
the main_loop is dominating all other threads in such a case that no other
threads are running unless there is activity on the panel of the application.
Doing this, it kills the functionality of using threads.

I will add my code so you can see for yourself what I mean. The mentioned
codepart is at the on_init of class MyApp < App


 

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=218&aid=12015&group_id=35