On Tuesday 05 January 2016 15:46:12 René J.V. Bertin wrote:
> Hi,
>
> An idea has come up, discussing with David Faure to develop a QProcess
> variant or a separate class ("QGuiProcess") to allow dependent code to
> start applications in proper fashion, taking platform specifics into
> account, such that the new application opens the way users of the platform
> would expect.
Sounds like the problem is elsewhere. If QProcess is not working, then maybe
the problem is how those processes expect parameters in the first place.
> For instance, starting an OS X application with a system() or fork()/exec()
> causes that application to open in the layer behind the one occupied by the
> calling process. This is easiest to see when starting an application from a
> terminal, say
>
> %> /Applications/Safari.app/Contents/MacOS/Safari
>
> the safari window(s) will open behind the terminal.
Right. You should open the bundle, not the executable inside it. That's not a
problem of QProcess, you just ran the wrong thing.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
