On Sun, May 15, 2011 at 07:25:43AM -0700, Albrecht Schlosser wrote: > > I *believe* that just calling Fl_Window::hide() would be more appropriate > here, and that checking the internal status, whether the window is still > shown (in the list of shown windows) would be enough to make sure that we > don't get into a recursion or something like that...
Ok, the exact thing on what to do is yet unclear ... > > OTOH, *if* this is possible, then this would be a way to circumvent the > window's close callback that is intended to give the application the > chance to do some cleanup (e.g. ask the user to save a file), and this > could seriously break the application logic. > >> This is such a fundamental change though that I will not allow it on the >> last Release Candidate just before a final release. I push this to 1.4 >> where we can have much more testing time. I can understand this. Please be aware that until now, the application just 'hangs' waiting on events for windows that don't exist anymore. I do believe such situation would be reported when it happens. Since no reports exist, I conclude that most testing is done in very safe environments ... Kurt _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
