The command wx.Window.Destroy() does not destroys the window at once, but adds it to a list to be deleted on idle time.
But if one needs not be encumbered by flotsam and jetsam of windows not yet destroyed, is there a command that obliterate them immediately or tells the application to wait until the actual destruction has been carried out?
raffaello wrote:
The command wx.Window.Destroy() does not destroys the window at once, but adds it to a list to be deleted on idle time.
But if one needs not be encumbered by flotsam and jetsam of windows not yet destroyed, is there a command that obliterate them immediately or tells the application to wait until the actual destruction has been carried out?
First, it's only the top-level windows (frames and dialogs) that have this delayed destruction feature, the others are destroyed immediately. It's possible that might change someday, but I doubt it.
Second, what exactly is the problem with having them stick around for a few milliseconds? Would hiding them before the Destroy solve it for you?
ยทยทยท
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!