[Development] A new approach for Qt main()

Thiago Macieira thiago.macieira at intel.com
Mon Dec 12 17:28:54 CET 2016

On segunda-feira, 12 de dezembro de 2016 11:07:56 PST Benjamin TERRIER wrote:
> 2016-12-12 10:56 GMT+01:00 Mark De Wit <mark.dewit at iesve.com>:
> > I have an application based on qt-solutions qtwinmigrate sample.
> > 
> > Because we're integrating Qt into an existing MFC application, we're not
> > even running QApplication exec.   The application uses MFC's entry point
> > for startup and drives the Qt event loop manually as part of the MFC
> > event loop.
> > 
> > Mark
> I also did something like that on Linux with a software written with
> another graphical framework.
> We made it work by calling QApplication::processEvents() in the other
> framework event loop.

Both cases are served by integrating the event loop of the foreign framework 
with Qt's. Doesn't matter how you start it (though I certainly prefer Qt's 
app.exec()), but you need to integrate.

processEvents() is not a solution. It's, at best, a crude hack.

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

More information about the Development mailing list