[Interest] Signals, slots before the event loop starts?

Thiago Macieira thiago.macieira at intel.com
Fri Apr 12 04:10:14 CEST 2019

On Thursday, 11 April 2019 06:44:40 PDT Jason H wrote:
> Thanks! If it's that easy, and more reliable, why doesn't qApp->quit() do it
> that way?

Because it is not "quitLater", it's "quitNow". The difference between those 
two things is the sequencing of the event loop interruption compared to other 
events, both those that have been received but not yet processed, and those 
being received right now. And the overhead, of course.

Your idea is valid, but it's not how the behaviour is today. Changing the 
behaviour could break existing applications. If you can easily do what you 
want with a simple QMetaMethod::invokeMethod call, I don't think we should 
change the existing function.

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel System Software Products

More information about the Interest mailing list