[SciPy-dev] gui_thread issue
prabhu_r at users.sf.net
Fri Nov 5 12:00:16 CST 2004
>>>>> "PP" == Pearu Peterson <pearu at scipy.org> writes:
PP> gui_thread.register is wrapped in gui_thread.__init__ to
PP> return its argument. So, modal_sample is acctually using the
PP> new approach.
Oh, OK. :)
>> Should we just remove all references to the old way and make
>> the new way the default? The old code will still be useful so
>> perhaps we create an 'old' directory and move stuff there?
>> So what is the consensus on this?
PP> I'd remove the old code since it didn't work well and clean up
PP> code that uses gui_thread.
PP> Btw, is there any reason that gui_thread.start() should not be
PP> executed while importing gui_thread? People tend to forget
PP> executing gui_thread.start().
The trouble is if you want to access gui_thread functionality without
starting the secondary thread. If I am not mistaken, if
gui_thread.start() was called on import and wx was already imported,
the import would fail and you can't import anything inside gui_thread.
More information about the Scipy-dev