To: garrigue at kurims.kyoto-u.ac.jp
Cc: checker at d6.com, lablgtk at kaba.or.jp
Subject: Re: resize event?
In-Reply-To: <20010105184946H.garrigue at kurims.kyoto-u.ac.jp>
References: <4.3.2.7.2.20010105002151.00baf5c0 at shell16.ba.best.com>
	<20010105184946H.garrigue@kurims.kyoto-u.ac.jp>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010105194456C.wakita at is.titech.ac.jp>
Date: Fri, 05 Jan 2001 19:44:56 +0900
From: Ken Wakita <wakita at is.titech.ac.jp>
Lines: 23


In message (<20010105184946H.garrigue@kurims.kyoto-u.ac.jp>)
from Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>,
talking about "Re: resize event?",
on Fri, 05 Jan 2001 18:49:46 +0900

> Thanks to this information, I think that I understand at last what's
> happening. Lablgtk's examples use directly the X window from the
> toplevel window, while GTK's example use a drawing area. One
> consequence is that the handling of events gets mixed with the
> handling on the toplevel window, meaning that according to the order
> in which events are called the drawing may be deleted immediately.

According to my event log, the only interesting events occuring are
[expose] and [configure].  As use-defined event handlers behave the
same for both events in the Chris's program the order of events seems
to be irrelevant.  I modified the event handlers to return false value
trying to prevent further handling of the event.  But the result was
the same.  It seems the handling on the toplevel window is hard coded
(not implemented via the standard event handling) and executed after
user-defined event handlers.

Ken