[Interest] Thread guarantee on slots+timers

Sensei senseiwa at gmail.com
Tue Apr 15 13:35:52 CEST 2014


On 14/04/14 13:04, André Somers wrote:
> No, then you misunderstood the above. If you use an auto connection (the
> default) or a queued connection to hook up your GUI thread to the slot,
> you have fulfilled the criteria for the slot to be only triggered from
> within the same thread, and thus stricktly consecutively*. So if you can
> fulfil this simple condition, you would *not* need to use a mutex to
> make sure your slot does not get called twice at the same time.
>
> André
>
> *) barring recursion or a processEvents() call, of course. Then all bets
> are off again.


Ok, thank, now it's completely clear! Fortunately, I followed the 
advices about using emit to trigger another thread, so I'm safe.

Thanks! :)




More information about the Interest mailing list