Re: Force destroying dialogs

'Pyfips' via wxPython-users wrote:
>
> I have a question regarding the wx.Window.Destroy() function in unit 
> tests.
> The documentation says, that this does not destroy windows immediately 
> but queues them for later deletion.
> Currently, I run into problems with GDI handles, since the dialogs are 
> not destroyed properly. The wx.App.Mainloop is not executed as there 
> are unit tests and events are processed during the test.

That's really a design flaw in the application.  Long-running tasks 
should be in a separate thread, specially to allow the UI to be 
responsive.  You have to get back to the main loop to allow the 
windowing subsystem to do its job.

It's a hack, but have you tried wx.Yield?

-- 
Tim Roberts, [email protected]
Providenza & Boekelheide, Inc.


-- 
You received this message because you are subscribed to the Google Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/wxpython-users/5f3e8a7e-24cb-8747-b341-83087e7e5056%40probo.com.