Update on this:
It didn't work. I called it, nothing (discernable) happened. Got a bunch of serial port not open errors....
Sent: Thursday, April 11, 2019 at 9:44 AM
From: "Jason H" <[email protected]>
To: "Konstantin Shegunov" <[email protected]>
Cc: "Interests Qt" <[email protected]>
Subject: Re: [Interest] Signals, slots before the event loop starts?
From: "Jason H" <[email protected]>
To: "Konstantin Shegunov" <[email protected]>
Cc: "Interests Qt" <[email protected]>
Subject: Re: [Interest] Signals, slots before the event loop starts?
Thanks! If it's that easy, and more reliable, why doesn't qApp->quit() do it that way?
Sent: Thursday, April 11, 2019 at 8:54 AM
From: "Konstantin Shegunov" <[email protected]>
To: "Jason H" <[email protected]>
Cc: "Giuseppe D'Angelo" <[email protected]>, "Interests Qt" <[email protected]>
Subject: Re: [Interest] Signals, slots before the event loop starts?
From: "Konstantin Shegunov" <[email protected]>
To: "Jason H" <[email protected]>
Cc: "Giuseppe D'Angelo" <[email protected]>, "Interests Qt" <[email protected]>
Subject: Re: [Interest] Signals, slots before the event loop starts?
On Thu, Apr 11, 2019 at 3:48 PM Jason H <[email protected]> wrote:
What is the best way to do that? I think in the past, I used a 0ms timer, but that always feels janky.
QMetaObject::invokeMethod(qApp, &QCoreApplication::quit, Qt::QueuedConnection);
is my preference.
_______________________________________________ Interest mailing list [email protected] https://lists.qt-project.org/listinfo/interest
