>
> Here is a patch that eliminates the blink of border color when a window
> is closed.
>
> This is not the most elegant solution, but it shows that the problem is
> the order in which the window is closed.
>
> ------------------------- fvwm-2.0.42-NoBlink.patch --------------------------
> --- builtins.c.orig Wed Apr 10 12:38:25 1996
> +++ builtins.c Fri May 3 11:02:22 1996
> _at_@ -598,6 +598,7 @@
>
> if (tmp_win->flags & DoesWmDeleteWindow)
> {
> + XUnmapWindow(dpy, tmp_win->frame);
> send_clientmessage (tmp_win->w, _XA_WM_DELETE_WINDOW, CurrentTime);
> return;
> }
> --
> Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
> To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
> message to majordomo_at_hpc.uh.edu.
> To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
>
Ah yes, you can do that, and it's reasonably elegant, but it doesn't solve the
problem entirely.
In fact, I was looking at the problem from the other point of view where the
application destroys its own window, leaving the frame window behind. How does
the window manager trap that before it happens. I now believe it cannot. I
think it can only wait until it gets the UnmapNotify or the DestroyNotify
through the SubstructureRedirectMask.
Cheers,
Jonathan.
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Fri May 03 1996 - 12:01:06 BST