Delivered-To: lablgtk at yquem.inria.fr
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Subject: RE : [Lablgtk] Strange firing of Configure and Expose events
	withEventBox
Date: Fri, 2 May 2008 11:12:40 +0200
Message-ID: <5EFD4D7AC6265F4D9D3A849CEA92191901415D at LAXA.intra.cea.fr>
Thread-Topic: RE : [Lablgtk] Strange firing of Configure and Expose events
	withEventBox
Thread-Index: AcisIHfuASDsRrrERB6Qrt4CBi+saAAEukgA
References: <20080501012417.59a99d33.pdgroves at gmail.com><5EFD4D7AC6265F4D9D3A849CEA92191901415C at LAXA.intra.cea.fr><20080501190305.e7de7684.pdgroves at gmail.com>
	<20080502014814.16c1c761.pdgroves@gmail.com>
From: "MONATE Benjamin 205998" <Benjamin.MONATE at cea.fr>
To: "Peter Groves" <pdgroves at gmail.com>
Cc: lablgtk at yquem.inria.fr
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Length: 459

Hi,
In cased you need further investigation, to have a window show up you =
have to use
the lablgtk2 script: "lablgtk2 eventbox.ml".
Your tests suggests that the drawing area default callback catched the =
expose events.=20

By the way AFAIK latest version of lablgtk2 do compile with 3.09.2.

Benjamin Monate


_______________________________________________
Lablgtk mailing list
Lablgtk@yquem.inria.fr
http://yquem.inria.fr/cgi-bin/mailman/listinfo/lablgtk