Re: unmap/map bug

From: Claude Lecommandeur (claude.lecommandeur@epfl.ch)
Date: Tue Sep 04 2001 - 14:08:03 CEST


   Hi,

   I am not surprised at all by this behaviour. The MapRequest and Reparenting
used by ctwm (amd most window managers) is prone to race conditions. I'm not
sure the window is destroyed, I think it is not mapped after the XMapWIndow and
the MapNotify is never received. You are welcome to find a fix for this, but this
is not a very serious problem.

    Claude.

Bj|rn Englund wrote:
>
> create and map a window (win)
>
> then run the following loop
>
> while(1) {
> XUnmapWindow(dpy, win);
> /* Wait for window to become unmapped */
> do {
> XNextEvent(dpy, &ev);
> } while(ev.type != UnmapNotify);
>
> XMapWindow(dpy, win);
> /* wait for the window to become mapped */
> do {
> XNextEvent(dpy, &ev);
> } while(ev.type != MapNotify);
> }
>
> the window will be destroyed after a few loops..
>
> /Björn

-- 
Claude Lecommandeur           Claude.Lecommandeur@Epfl.Ch
EPFL - SIC                    +41 21 693 22 97
1015 Lausanne (Switzerland)   http://slwww.epfl.ch/SIC/SL/info/Claude.html

sh: fortune: not found.



This archive was generated by hypermail 2.1.2 : Sat Jun 22 2002 - 06:45:02 CEST