[SOLVED] QProcess
-
Hello all,
I am about to start a project where I have my Qt GUI and another process (motion control application) that I will be communicating with using QSharedMemory. I was curious whether it is better to spawn my motion control process from my Qt GUI process, or have my Qt GUI process from my motion control application. I am not sure if there is a difference and would like to know if anyone has any thoughts or opinions on the matter. Performance of my non-Qt application is critical.
Thank you :)
-
I would say it is more natural to have the GUI application launch the motion control application, as the former is visible to the user and the latter is running in the background (I assume). Would be kind of strange if a process running in the background suddenly launcher another process that pops up a GUI window. The other way a round, i.e. the user launcher a GUI program and then that program creates more "helper" processes in the background, it is more common. Also, the Non-Qt app can not make use of QProcess, obviously.
Alternative: What about running your "motion control application" as a system service or at least put it into the Autostart? For example it could be running as a "system tray" application. This way, the background application is already running and the GUI just connects to it...
-
[quote author="MuldeR" date="1369782229"]I would say it is more natural to have the GUI application launch the motion control application, as the former is visible to the user and the latter is running in the background (I assume). Would be kind of strange if a process running in the background suddenly launcher another process that pops up a GUI window. The other way a round, i.e. the user launcher a GUI program and then that program creates more "helper" processes in the background, it is more common. Also, the Non-Qt app can not make use of QProcess, obviously.
Alternative: What about running your "motion control application" as a system service or at least put it into the Autostart? For example it could be running as a "system tray" application. This way, the background application is already running and the GUI just connects to it...[/quote]
Sounds good. Thanks!