Re: Re: FVWM: TODO List comment

From: <Jonathan_Monahan_at_HP-Pinewood-om1.om.hp.com>
Date: Tue, 7 May 96 11:45:29 +0100

> What I think is happening is that the X-server is painting the frame
> with it's background colour when the client window disappears. I haven't
> looked at the window frame creation code but I suspect from these symptoms
that
> it is given a background colour in order to speed up refreshes (only the
> non-background bits need to be drawn by fvwm).
>

Yup, that's exactly what I was thinking.

> Since fvwm can't stop clients unmapping themselves and can't stop the server
> filling in the background colour when the frame centre is exposed the only
> way to stop the flashing is to make sure the area under the client window
> has a background of none.
>
> There are two ways to do this, either don't set the frame background and live
> with the extra drawing overhead or create an intermediate window with no
> background under the client but above the frame.
>
> When there is no background for the server to paint the screen will be left
> with the contents of the client window until the frame is unmapped.
>

Nifty. Yes, I think this might just work. I guess the only disadvantage is if
the window manager or comms lock up straight after the client exits, in which
case, the user will be left with a client that looks OK, but doesn't respond at
all. But, then that's no bad thing really, because whatever you do to it, it
won't cause any problems.

My vote would be for the extra window. I know that adds a lot of extra windows
(one per client window), but we are not trying to solve the problem for fast
machines. The situation that needs resolving is the one where the
machine/network is slow, in which case we NEED the background colour to minimise
repainting work, but we also need the extra window with background colour none
to avoid the flash.

> Hope this helps,
> Tim Phipps.

Well done ! Nice bit of round-about thinking.

  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 Tue May 07 1996 - 05:36:54 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:58 BST