But what does waitForDisconnected() do for you? I don't see any point in using it... You have a slot connected to the disconnected() signal, so why wait for the signal in a busy loop?
This is obvious, because timers won't fire and the state won't be able to change.
Maybe processEvents() is wise enough to call the appropriate event queue based on the current thread id and thanks to that your application doesn't crash...






rocessEvents();
Reply With Quote
Bookmarks