From: Richard Dale <Richard_Dale@...>
Date: 2005-10-29T22:32:05+09:00
Subject: Re: Qt Threading?

gregarican wrote:

> gregarican wrote:
> 
>> The problem is that the threads don't seem to work independently. The
>> listener thread won't advance until the Qt application has processed a
>> couple of events. So the seconds don't count up in real-time. This
>> takes place on a Win32 platform, so I don't think I can use a fork
>> method to split things off independently.
Ruby doesn't use native threads, and so as far as Qt is concerned you have a
single threaded application. Only when the Qt runtime calls say a ruby slot
in your code, will ruby be able to schedule the background thread to run. 

> 
> I did stumble across -->
> http://lists.trolltech.com/qt-interest/1997-06/thread00137-0.html,
> which details how to implement QSocketNotify. I am assume this might be
> the way to go?
Yes, it is. That way you don't need an extra thread, and you can detect any
input on the socket as part of the normal Qt event loop. But you didn't
describe quite what you wanted to monitor in your original post, I didn't
know what you meant by 'incoming signals'.

-- Richard