DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2627 Version: 1.4-feature Bill wrote: > I would destroy the Fl_X object right away on the XDestroyWindow > message. That would remove the need for this test. Then call the close > event, then perhaps show the window again, like you are doing. I don't see how to do that because window->hide() must be called for structures pointed to by the Fl_X object (e.g., dble buffer, clip region) to be properly deallocated when this object is deleted. Then, the FL_CLOSE event is processed, and then I don't see how to know if the application wants the window recreated or not. The attached destroynotify4.patch is a better solution than before that avoids the introduction of a global variable. Link: http://www.fltk.org/str.php?L2627 Version: 1.4-feature _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
