> > Hi all,
> > I was just scanning through the TODO list on the Homepage when I
> > noticed the following line:
> > - Find out why closing windows fills the area w/ the border color
> [...]
> > I guess the only way to stop this is to trap the fact that the client
> > window is going to be destroyed or hidden and then apply the same
> > function to the Frame first and then the client window.
>
> Does that work?
>
> --
> Todd Fries
> --
> 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.
>
Well, this is where I'm a little unsure. As I said, my knowledge of window
manager level X code is not wonderful, but I thought that a window manager could
get notification of all X calls...
...searching for an X manual to grab off a colleague...
Aha ! Here it is... SubstructureRedirectMask... Oh. No. Perhaps not...
SubstructureRedirectMask only gets MapRequest, not Unmap...
Oh, well I suppose you're right then, no it doesn't work.
Anyway, I think my explanation of why the frame window gets cleared to the
background colour of the frame still stands. Only, I guess we've just proved
that you cannot do anything about it, so presumably it could be taken off the
TODO list. (I'm trying to save you some work here Chuck ;-)
Sorry for the false alarm,
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 - 09:41:32 BST