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 OK< after reading some docs on this, I understand that this is sent when the app requests that windows are destroyed, and then they actually are destroyed by the client. In the normal use case, the corresponding FLTK classes are destroyed at the same tome by the FLTK core code. Sending an additional message may or may not cause confusion if FLTK destroyed the classes before the WM destroys the windows. This is not to say that we should ignore this message. It would probably be wise to tell the corresponding FLTK class (if it still exists) that the underlying X11 window has vanished and can no longer be accessed. 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. 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
