On Wednesday, May 23, 2001, at 01:18 , David Given wrote:
> One of the things I want to use this for is to have an engine thread
> doing work
> in the background. When the work is completed, it can send a message to
> the UI
> thread telling it where the results are. The message arrives on the
> input queue
> and is processed with all the other X events. Yes, I know I can do this
> with
> semaphores and mutexes but that restricts me to using a thread in the
> same
> process, which may not be the case. Besides, I don't know of any way of
> integrating semaphore blocking into the GDK event loop.
So you want an engine process that has no UI running on one machine to
be able to talk to a UI process on another machine. I'd use BSD sockets
and input_add for that, myself, rather than rely on the X server (fewer
things that can break that way). But if I had to do something like that
(as in someone told me I had to use that particular X facility), I'd
look at how it's done in X, then look for something similar in GDK, then
look for its counterpart in PyGtk. If it's missing at any of these
points, then you'll need to do something else.
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
