[Interest] Is QEventPrivate a remnant?

[Nye]

Hello,
Sorry for continuing to bug you with this, but I don't seem to grasp how to
run QCoreApplication in non-blocking mode.
Looking here:
http://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/kernel/qcoreapplication.h#n113
and here:
http://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/kernel/qeventdispatcher_unix.cpp#n581
It looks like the aforementioned signal will be emitted only if the event
loop is about to block, and judging by the statics defined in
QCoreApplication I can't set the event processing flags globally.

The only way I could fathom to do this would be to run a second event loop
by means of QEventLoop and there just run it non-blocking. Something like
this:
QEventLoop myLoop;
myLoop.exec(QEventLoop::AllEvents & ~QEventLoop::WaitForMoreEvents);

Am I correct, or there's a better way?

Kind regards.

On Sun, Feb 14, 2016 at 1:53 AM, Thiago Macieira <thiago.macieira at intel.com>
wrote:

> On sábado, 13 de fevereiro de 2016 11:17:22 PST Nye wrote:
> > Thanks! However I'm still going to need to run the dispatcher (default or
> > not) in non-blocking mode, right? Or am I missing something?
>
> Always non-blocking.
>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel Open Source Technology Center
>
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20160214/4db70e9e/attachment.html>