[Qt-interest] Qt signaling smarts...

[BRM]

----- Original Message ----

Scott Aron Bloom wrote:
> You will be covered.. Before a QObject derived class is destroyed, it
> emits a "destroyed()" signal, all objects connected to it, disconnect
> from it at that point.

Please re-read my original e-mail, as you seem to have missed the question.

I know that the signaling will work - that at the very least thread1 will send messages to mainProgram which will send it to thread2.

My question is:

Is the Qt Signal/Slot mechanism smart enough to figure out that the thread1 could be sending directly to thread2, and bypass the mainProgram signal altogether (since it's all just signals triggering each other)?
OR is it at least smart enough that it will not invoke the event loop in mainProgram when delivering the signal from thread1 to thread2?

In my actual program, thread1 is going to be generating a lot of data that may go to multiple instances of thread2;
and I would rather not have to have all that data get crammed through program's main thread and main event loop,
but instead go directly to the thread2's event loop.

TIA,

Ben