On mardi 03 février 2009, Giovanni Bajo wrote:
> > In this last case, does the call to emit() immediatly return, and the
> > thread go on with the next instruction, or does it wait until the
> > event has really called the slot?
>
> Depends on the connection type (which you can manually specify during
> the connect() call, or leave the default).
>
> The default (for connections between different threads) is
> Qt.QueuedConnection, which means that the emit() call exits immediately.
> Otherwise, you can specify Qt.BlockingQueueConnection: the emitting
> thread will wait until the receiving thread has found time to process
> all the slots.
Ok (Qt is really powerfull!).
> Notice that it's easy to deadlock, if you don't pay enough attention (and
> even if you do ;).
Why do you say it is easy to deadlock? Do you mean that Qt can do
unexpected things?
--
Frédéric
http://www.gbiloba.org
_______________________________________________
PyQt mailing list PyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
