On Monday, 29 October 2018 07:24:25 PDT Jeffrey Brendecke wrote:
> It looks like it means that as long as I run QCoreApplication::exec() on its
> own thread, that I can do all the Qt event handling/signal slot connections
> I want on that thread and not worry about what's going on on the main
> thr
>
> On Sunday, 28 October 2018 08:58:57 PDT Jeffrey Brendecke wrote:
>> Is it possible to have a 100% native UI (Cocoa or UIKit) with backend QtCore
>> components (nonGUI) on a functioning event loop for signals and slots on
>> macOS and iOS?
>
> Sure. But you need to integrate the event loops,
The signal/slot mechanism does not always requires Qt eventloop. So, you
can use QtCore directly without any other works.
But QtNetwork requires eventloop to dispatch network IO events. You'd
better use other network toolkit then.
In fact, the signal/slot connection with Qt::QueuedConnection type
On Sunday, 28 October 2018 08:58:57 PDT Jeffrey Brendecke wrote:
> Is it possible to have a 100% native UI (Cocoa or UIKit) with backend QtCore
> components (nonGUI) on a functioning event loop for signals and slots on
> macOS and iOS?
Sure. But you need to integrate the event loops, so one of the
