This is my scenario: I have a dll (with Qt in the back-end, and with no event loop started). I am able to perform the signal-slot communication with-in this dll (there is a only one thread). I would like to use the facilities of QFileSystemWatcher in this dll. But it looks like, QFileSystemWatcher starts its own thread, and it is not able to communicate to my main thread since there is no event process.
So, basically I need a way to start the event processing without being blocked !
So, basically you want to use
QEventLoop
features without using theQEventLoop
based on the comment discussion. TheQEventLoop
has to be "blocking", inherently, in order to actually have an event loop.You could always create a "blocking" thread with the event loop inside, but then your signal-slot management might be tied to that particular thread.
This is not the usual way of using an event loop, but depending on your concrete scenario, it might be sufficient in this special case.