To: jehenrik at yahoo.com
Cc: lablgtk at kaba.or.jp
Subject: Re: answer to "Thread wedge in lablgtk" is for a different question
In-Reply-To: <001401c10396$950e3ac0$0b01a8c0 at mit.edu>
References: <20010703113844V.garrigue at kurims.kyoto-u.ac.jp>
	<001401c10396$950e3ac0$0b01a8c0@mit.edu>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010703184927P.garrigue at kurims.kyoto-u.ac.jp>
Date: Tue, 03 Jul 2001 18:49:27 +0900
From: Jacques Garrigue <garrigue at kurims.kyoto-u.ac.jp>
Lines: 20

From: "Jeff Henrikson" <jehenrik@yahoo.com>

> My message was actually a reference to one I sent a few days before.
> The "pointer motion" discrepancy between Linux and Windows was a
> comment on the old rather than a new problem.  (See the earlier
> message.)  All I want to do is get a thread to trigger a paint
> message.  But what happens is that after the first paint, the thread
> that sends periodic paint messages gets stuck.

Sorry, I didn't understand your problem.

The answer is even simpler: with threads, you must use GtkThread.main
in place of GMain.Main.main, otherwise the gtk mainloop will lock.
If you use the toplevel, a thread is automatically started, so you
will have two mainloops running simultaneously, but that seems OK (I'm
wondering why...)

Cheers,

Jacques