Program freezing on quit (frame waiting for idle before destroy()?)

wxPython Users
1

Hi all,

I have read somewhere that when destroy() is called on a frame, wxPython
will wait for an idle moment before actually destroying it.

In our small app, if we call a logout() function by selecting it in a
menu and than call a quit() function the same way, the program closes
and everything is ok.

But if we actually kill the application using alt-F4 or the X button, we
have an onQuit() event function that will call logout(), and then
destroy all children frames before destroying the main frame, and then
calling a system.exit()

The problem is that in that case, our server gets the logout() message,
but the client GUI is frozen. It’s like if wxPython cannot find an
“idle” moment to actually destroy the frames maybe?

Any workaround for this?

Thanks

Michel Martin
Baccalauréat en informatique
Université de Sherbrooke
Courriel: <mailto:michel.martin@usherbrooke.ca>
michel.martin@usherbrooke.ca
Site Web: <http://www.michelmartin.ca> http://www.michelmartin.ca
"True love is born from understanding." The Buddha