<![CDATA[[SOLVED] Wait for timeout or some signal]]>Hi All!
I need send some message by the local net, and than need wait to some answer or exit at the function by timeout,
I try stop by forever loop, and there wait some signals, but no signal is comming (i think thats because i create this loop at the main thread), i want to try create wait loop and timeout timer not at the main threads, but i don't like this idea, some one can tall me easy way to resolve this problem?

]]>https://forum.qt.io/topic/12742/solved-wait-for-timeout-or-some-signalRSS for NodeSun, 06 Sep 2026 15:26:36 GMTTue, 03 Jan 2012 09:33:31 GMT60<![CDATA[Reply to [SOLVED] Wait for timeout or some signal on Fri, 31 Oct 2014 09:54:45 GMT]]>[quote author="Andre" date="1357286986"]Yes, I know where to find the sources and I know the docs, but that was not my question. I sometimes use this idea:
@
QEventLoop loop;
connect(myObject, SIGNAL(theSignalToWaitFor()), &loop, SLOT(quit()));
connect(timeoutTimer, SIGNAL(timeout()), &loop, SLOT(quit()));
loop.exec(); //blocks untill either theSignalToWaitFor or timeout was fired
@

[/quote]

thank you. it's very useful.

]]>https://forum.qt.io/post/126739https://forum.qt.io/post/126739Fri, 31 Oct 2014 09:54:45 GMT<![CDATA[Reply to [SOLVED] Wait for timeout or some signal on Fri, 04 Jan 2013 08:09:46 GMT]]>Yes, I know where to find the sources and I know the docs, but that was not my question. I sometimes use this idea:
@
QEventLoop loop;
connect(myObject, SIGNAL(theSignalToWaitFor()), &loop, SLOT(quit()));
connect(timeoutTimer, SIGNAL(timeout()), &loop, SLOT(quit()));
loop.exec(); //blocks untill either theSignalToWaitFor or timeout was fired
@

]]>https://forum.qt.io/post/126074https://forum.qt.io/post/126074Fri, 04 Jan 2013 08:09:46 GMT<![CDATA[Reply to [SOLVED] Wait for timeout or some signal on Thu, 03 Jan 2013 19:46:59 GMT]]>See "this":http://dev.libqxt.org/libqxt/src/21ea5919eabb2a404eafdffcdb8383472ca66bdd/src/core/qxtsignalwaiter.cpp?at=master#cl-143 and read the doc about WaitForMoreEvents "here":http://qt-project.org/doc/qt-4.8/qeventloop.html#ProcessEventsFlag-enum.

]]>https://forum.qt.io/post/126070https://forum.qt.io/post/126070Thu, 03 Jan 2013 19:46:59 GMT<![CDATA[Reply to [SOLVED] Wait for timeout or some signal on Thu, 03 Jan 2013 15:35:43 GMT]]>[quote author="RomaHagen" date="1357227120"]QxtSignalWaiter is implemented with a help of processEvents, not eventLoop. See "here":http://dev.libqxt.org/libqxt/src/21ea5919eabb2a404eafdffcdb8383472ca66bdd/src/core/qxtsignalwaiter.cpp?at=master#cl-143. [/quote]

Hmmm... You're right. Surprising. Thanks for the correction.

Does anyone know why Qxt choose this implementation instead?

]]>https://forum.qt.io/post/126069https://forum.qt.io/post/126069Thu, 03 Jan 2013 15:35:43 GMT<![CDATA[Reply to [SOLVED] Wait for timeout or some signal on Thu, 03 Jan 2013 15:32:00 GMT]]>QxtSignalWaiter is implemented with a help of processEvents, not eventLoop. See "here":http://dev.libqxt.org/libqxt/src/21ea5919eabb2a404eafdffcdb8383472ca66bdd/src/core/qxtsignalwaiter.cpp?at=master#cl-143.

]]>https://forum.qt.io/post/126068https://forum.qt.io/post/126068Thu, 03 Jan 2013 15:32:00 GMT<![CDATA[Reply to [SOLVED] Wait for timeout or some signal on Tue, 03 Jan 2012 17:49:08 GMT]]>@Andre,
Thanks, feel like got good things to know and even another useful-looking library!

]]>https://forum.qt.io/post/122664https://forum.qt.io/post/122664Tue, 03 Jan 2012 17:49:08 GMT<![CDATA[Reply to [SOLVED] Wait for timeout or some signal on Tue, 03 Jan 2012 13:13:28 GMT]]>Calling processEvents() in a loop like proposed will keep your CPU 100% bussy, because you just keep polling the event queue. Using an eventloop is a smarter solution that doesn't waste CPU cycles like that, so it will not spike your CPU. It is also the solution implemented by the libQxt in QxtSignalWaiter.

]]>https://forum.qt.io/post/122626https://forum.qt.io/post/122626Tue, 03 Jan 2012 13:13:28 GMT<![CDATA[Reply to [SOLVED] Wait for timeout or some signal on Tue, 03 Jan 2012 13:05:34 GMT]]>@rich,
Can hear more details of using processEvents() and QEventLoop story here?

]]>https://forum.qt.io/post/122624https://forum.qt.io/post/122624Tue, 03 Jan 2012 13:05:34 GMT<![CDATA[Reply to [SOLVED] Wait for timeout or some signal on Tue, 03 Jan 2012 12:13:11 GMT]]>Please don't use processEvents() like this, or your CPU usage will be terrible. Instead use QEventLoop.

]]>https://forum.qt.io/post/122612https://forum.qt.io/post/122612Tue, 03 Jan 2012 12:13:11 GMT<![CDATA[Reply to [SOLVED] Wait for timeout or some signal on Tue, 03 Jan 2012 10:37:08 GMT]]>tnx a lot!

]]>https://forum.qt.io/post/122595https://forum.qt.io/post/122595Tue, 03 Jan 2012 10:37:08 GMT<![CDATA[Reply to [SOLVED] Wait for timeout or some signal on Tue, 03 Jan 2012 10:30:31 GMT]]>Or, look into "QxtSignalWaiter":http://libqxt.bitbucket.org/doc/0.6/qxtsignalwaiter.html from the libQxt library.

]]>https://forum.qt.io/post/122593https://forum.qt.io/post/122593Tue, 03 Jan 2012 10:30:31 GMT<![CDATA[Reply to [SOLVED] Wait for timeout or some signal on Tue, 03 Jan 2012 09:48:54 GMT]]>tnx, i note that!

]]>https://forum.qt.io/post/122586https://forum.qt.io/post/122586Tue, 03 Jan 2012 09:48:54 GMT<![CDATA[Reply to [SOLVED] Wait for timeout or some signal on Tue, 03 Jan 2012 09:47:37 GMT]]>Yeah, it forces the QCoreApplication instance to process events in the event queue, including signals and slots provided by MOC. This way, the loop does not block operation of the app.

]]>https://forum.qt.io/post/122584https://forum.qt.io/post/122584Tue, 03 Jan 2012 09:47:37 GMT<![CDATA[Reply to [SOLVED] Wait for timeout or some signal on Tue, 03 Jan 2012 09:46:05 GMT]]>WOW so easy? i'll try that :) thnx

]]>https://forum.qt.io/post/122585https://forum.qt.io/post/122585Tue, 03 Jan 2012 09:46:05 GMT<![CDATA[Reply to [SOLVED] Wait for timeout or some signal on Tue, 03 Jan 2012 09:44:47 GMT]]>@
forever {
doMyLogic();
qApp->processEvents();
}
@

]]>https://forum.qt.io/post/122583https://forum.qt.io/post/122583Tue, 03 Jan 2012 09:44:47 GMT