forked from qt-creator/qt-creator
ProjectExplorer: Switch responsibilities for raising applications
Instead of letting the launcher decide to raise something when started (and only then) leave it to the RunControl to trigger (and for now also to implement) as response to the application launcher start (or possibly now, in other circumstances). Change-Id: I0ac8f1e633981f7bf316c88e83c208765886d9a1 Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
This commit is contained in:
@@ -770,8 +770,6 @@ PythonRunControl::PythonRunControl(PythonRunConfiguration *rc, Core::Id mode)
|
||||
this, &PythonRunControl::processStarted);
|
||||
connect(&m_applicationLauncher, &ApplicationLauncher::processExited,
|
||||
this, &PythonRunControl::processExited);
|
||||
connect(&m_applicationLauncher, &ApplicationLauncher::bringToForegroundRequested,
|
||||
this, &RunControl::bringApplicationToForeground);
|
||||
}
|
||||
|
||||
void PythonRunControl::start()
|
||||
@@ -815,6 +813,7 @@ void PythonRunControl::processStarted()
|
||||
{
|
||||
// Console processes only know their pid after being started
|
||||
setApplicationProcessHandle(ProcessHandle(m_applicationLauncher.applicationPID()));
|
||||
bringApplicationToForeground();
|
||||
}
|
||||
|
||||
void PythonRunControl::processExited(int exitCode, QProcess::ExitStatus status)
|
||||
|
||||
Reference in New Issue
Block a user