Quote Originally Posted by ChrisW67 View Post
If the signals are cross-thread then they will be queued rather than the slot executing synchronously. Making the connections at line 37-41 Qt::QueuedConnection as they would be in the threaded scenario does not affect the performance. Perhaps you could produce a small example that more closely matches what you are doing.
Hi ChrisW67, Im using a plain connect so it should be detected and working as a queued connect as shows in the documentation. The next I will do is force a Qt::QueuedConnection instead of relaing in Qt::AutoConnection. On monday I will have a pc with visual studio and I will create an example. Its basicaly the same as the above message, but instead of a QTimer that emits the signals, is a plain OS thread. The thread just dequeues elements and calls emit. Does you see an issue to have 2 widgets parentless that interact? Is this the correct way to doit?


Thanks
Ramiro