On Mon, May 16, 2011 at 09:15:14AM +0100, MacArthur, Ian (SELEX GALILEO, UK)
wrote:
>
>
> > Ok, the exact thing on what to do is yet unclear ...
>
> Agree!
>
>
> > 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 ...
>
> Well, the way I read that is more that the lack of reports suggests that
> only the WM you are testing with does this thing, and all other WM do
> not...
almost. You should read: 'noone is using applications that do XDestroyWindow'
>
I started to notice this when I was creating a custom WM. This WM will
not expose this behaviour anymore, since I incorporated the WM_DELETE_WINDOW
atom.
But the behaviour of any FLTK app when XDestroyWindow (= legal X11 call) is
called
from any other X client is very wrong.
> The implication, then, would be that your WM is therefore in some way
> "abnormal", so it may be the WM rather than FLTK that is buggy and
> flawed here.
forget the WM
>
> What WM is it? Can we grab the sources and try it on other hosts?
Since I fixed the WM, forget the WM.
but any client that does XDestroyWindow will do, like:
#include <X11/Xlib.h>
#include <stdlib.h>
int main(int argc, char *argv[])
{
Display dpy;
Window xid;
dpy = XOpenDisplay(getenv("DISPLAY") ?: ":0");
XDestroyWindow(dpy, strtoul(argv[1], 0, 0));
XFlush(dpy);
return 0;
}
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
