Re: FVWM: FvwmPager goes crazy?

From: Dominik Vogt <fvwm_at_fvwm.org>
Date: Thu, 27 Feb 2003 16:39:46 +0100

On Thu, Feb 27, 2003 at 03:52:20PM +0100, Gert Brinkmann wrote:
> Dan Espen wrote:
>
> >VisibilityNotify and Expose.)
>
> Just for my understanding: What are the messages "VisibilityNotify" and
> "Expose" good for? Is it a mozilla bug that it reacts on only
> "VisibilityNotify"?

When an applications was partially or fully hidden and becomes
fully visible, the window gets a "VisibilityUnobscured" message.
If it was at least partially visible and becomes fully obscured,
it gets "VisibilityFullyObscured" and if it was fully visible or
fully obscured and becomes partially visible, it gets a
"VisibilityPartiallyObscured" message.

Especially, no event is sent when some parts of the window were
covered and some were not, and the window is moved so that other
parts are covered. However, Expose events are generated for the
newly uncovered areas (unless backing store is used).

> Perhaps this should be configurable as a Style somehow? Then fvwm was
> ICCCM compliant but the user can decide if this makes sense.

No. First, fvwm is not involved at all in these events. Second,
it is totally clear from any X documentation I read that
applications have to redraw in response to Expose events. An
application using VisibilityNotify in place of Expose is simply
broken.

Bye

Dominik ^_^ ^_^
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Thu Feb 27 2003 - 09:39:00 GMT

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