To: jehenrik at yahoo.com
Cc: lablgtk at kaba.or.jp
Subject: Re: Thread wedge in lablgtk: happens in linux too
In-Reply-To: <000b01c1012b$515f34e0$0b01a8c0 at mit.edu>
References: <000a01c100dd$5c7db840$0b01a8c0 at mit.edu>
	<000b01c1012b$515f34e0$0b01a8c0@mit.edu>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010703113844V.garrigue at kurims.kyoto-u.ac.jp>
Date: Tue, 03 Jul 2001 11:38:44 +0900
From: Jacques Garrigue <garrigue at kurims.kyoto-u.ac.jp>
Lines: 17

> I downloaded and built ocaml on my linux box to see if this bug was reproducible there.  With the default thread configuration, I
> didn't seem to be able to Thread.create to do anything except return a handle.  I'm not sure if this is normal.
> 
> Passing -with-pthread to configure and rebuilding, I got the identical result as under win98 with one observable exception: "mouse
> move" events don't appear to be enough to unwedge.  But "mouse entry" and "mouse click" are.  It has been a long time since I
> looked at the X mouse handling documentation, but I seem to recall you have to do something special to get sent mouse motion
> events.  I know win32 sends them to all applications.  So this makes sense.

Each widget has its defaults set of events it receives.
Apparently POINTER_MOTION is not in it. You can add it, just before
area#misc#realize ():

let w = area#event#add [`POINTER_MOTION]; ...

This gets your expected behavior.

Jacques