[Qt-interest] Qt signaling smarts...
BRM
bm_witness at yahoo.com
Tue Nov 24 20:11:47 CET 2009
Nothing wrong per se, I was just hoping to be able to avoid having to keep track of the current myQThread1 - as it comes and goes.
FYI - myQthread1 and myQthread2 are both QTcpSocket handling threads that come and go with the client connections.
Ben
----- Original Message ----
From: Dan White <ygor at comcast.net>
To: BRM <bm_witness at yahoo.com>
Cc: qt-interest at trolltech.com
Sent: Tue, November 24, 2009 1:08:47 PM
Subject: Re: [Qt-interest] Qt signaling smarts...
Is there anything wrong with saying, in the main program,
connect(&myQThread1,SIGNAL(thread1Signal()), &myQThread2, SIGNAL(thread2Signal()) ;
Thus bypassing the main thread ?
“Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin & Hobbes)
----- BRM <bm_witness at yahoo.com> wrote:
> That last one I was just re-stating the previous questions in slightly different terms.
>
> Thank you very much for answering my question. Looks like I will need to figure out how
> to track the QThread1 object so I can make queued connections directly between
> the two threads without having it go through the main thread.
>
> Thanks!
>
> Ben
>
>
> _______________________________________________
> Qt-interest mailing list
> Qt-interest at trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-interest
More information about the Qt-interest-old
mailing list