On Thu, May 12, 2011 at 12:03:34PM -0700, Ian MacArthur wrote: > > 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.3-feature > > > I don't know enough Xlib to be sure, but I had the impression that it was > sent in response to the app requesting that the window be closed. > > It seems that Kurt has a (possibly non-standard) WM that is sending these
I detected the problem with a non-standard WM, but that's the messenger here. Whenever XDestroyWindow is called by any external program, you're stuck. a WM is supposed to used WM_DELETE_WINDOW clientmessage, but no one says that XDestroyWindow() may not be called by anyone but the owner. > events to the app, at times when the app has not requested to close the > window, so the state between the WM and fltk is getting messed up, and > fltk does nothing with the DestroyNotify event that it is not expecting... > > Kurt's patch maybe fixes his use-case, but I am not sure if it is strictly > valid or not for the general case. > > On the other hand, it might be entirely harmless to do it anyway, so... I'm not sure if it's strictly valid to do neither, but FLTK keeps closer to what is happening on X (window destroyed), instead of hanging around with a window that will never get any events anymore. I considered that an improvement. Kurt _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
