Hi, Sorry, but I'm very stubborn, and because I didn't get answer on dabo-users, I started thread here :) I would like to share my thoughts about destroying of dialog frames (I started from dialogs, but all types of forms are affected) and ask your opinion. I have no reservations for form releasing when main event loop is in progress. It works as it should. But before application main loop starts, it seems to be a bit clumsy to me. First reservation is, that in this case safeDestroy() method is never called. It's because is deferred by callAfter() function. I don't know if it's necessary to defer it, since wx documentation claims, that Destroy() method is deferred in itself, to allow process all pending events. I tested pure self.safeDestroy() in place of callAfter(self.safeDestroy) call, and didn't found any negative results in my Dabo applications. Positive is that Destroy() method is called. Second reservation is, that dDataControlMixin.__onDestroy() events of controls aren't fired even with Destroy() properly called in such situation. Only chance my code will work, is to move it from onDestroy events to form closing() method. Everything I wrote is perfectly seen on example of application login dialog. Especially with more than one login attempts, where all instances of login dialog form aren't released until application main loop starts, after #1297 ticket corrected by Paul - thanks again. Before it, all of them stayed in memory until application close. All comments and suggestions are welcome.
-- Regards Jacek Kałucki _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
