From: cix <mcix@...>
Date: 2002-02-17T01:23:02+09:00
Subject: Re: Ruby threading and GUI toolkits

On Saturday 16 February 2002 16:17, you wrote:
> I've encountered a bit of a dilemma.  I need to have a GUI application with
> background threads handling communications (tcp, etc).  With the GUI
> toolkits I have seen you set them up (build windows/widgets) then you enter
> a message loop, and it locks the whole Ruby process (all other Ruby threads
> are "starved").  I know Lyle has something that lets this work on Fox (kind
> of...1.7 issues) but I was just wondering if anyone had any experience with
> allowing this GUI message loop to NOT lock up Ruby threads?  Are there any
> general strategies we could use to enable this across all of the GUI
> toolkits?
>
> -Rich
Hi Rich,
I do not understand exactly your question. The reason I write is that
I have just written a small program which is a talk-like application.
Each client has two threads, one getting charactes from the keybord, 
displayng them to the 'in' window (Tk text) and sending them to a socket, 
the other one reading  from the socket and displaying to the 'out' window.
The user can see the peer's messages while writing his owns.
If this behaviour is what you are talking about, could you describe the 
problem a little bit more in detail so that I can help in solving it?
Bye,
cix