Re: Xlib: unexpected async reply (sequence #####)!

[Chris Vine <chris cvine freeserve co uk>]

On Sat, 2007-08-04 at 22:07 +0800, Gregory Hosler wrote:
> That threads_enter/threads_leave doesn't look so bad, since I'm not doing alot
> of gtk withing my thread. Looks like it might be the way to go for me.

You may be missing the point.  If you access GTK+ from more than one
thread, then all operations with GTK+ need to protected with the GDK
lock, in any thread, including in the main GUI thread.  That is why
using g_idle_add() is often a better approach.

Chris