[Qt-interest] QT3's postEvent VS QT4's connect (blocking queued connection)

[Andreas Pakulat]

On 10.01.09 13:44:42, Neeraj Jhawar wrote:
> Sir,
> 
> The problem that I wish to solve is that QT system ( the new thread) takes
> regular inputs (at 100 ms interval) from RTLinux and shows it in the GUI. I
> have been able to design the connection between QT and RT in the thread but
> the problem comes when i try to show it in QT GUI. I need to show it every
> 100 or so ms and not more. But the postEvent application says it waits till
> the event is called and " The event will be delivered later on by the GUI
> thread." I dont want this. I need a constant connection between the threads
> SIGNAL and the SLOT which will be responsible to show the details in GUI. I
> had read this is possible by connect if you give is blocking queued
> connection.

Then why are you using a separate thread at all? If your GUI is supposed to
block while you fetch the data just do the data-fetching inside the GUI
thread. That'll remove all needs for cross-thread-communication.

Andreas

-- 
Tonight's the night: Sleep in a eucalyptus tree.