diff options
| author | hjk <hjk@qt.io> | 2017-03-13 13:48:55 +0100 |
|---|---|---|
| committer | hjk <hjk@qt.io> | 2017-03-24 13:37:46 +0000 |
| commit | 2360a2d743514014db57ec143c5ff1b469e5ada1 (patch) | |
| tree | 9a52695e0d5a13898fabd95aa33e13bccbe2117a /src/plugins/ios/iosruncontrol.cpp | |
| parent | 1a416d3f982d1fc574c578fdd6bafce51714f8a3 (diff) | |
| download | qt-creator-2360a2d743514014db57ec143c5ff1b469e5ada1.tar.gz | |
ProjectExplorer: Run RunControl::{start,stop} always asynchronously
This introduces a mini-state-"machine" to handle RunControl states
Intialized->[Starting->Running->Stopping->Stopped->]*->Finished.
Needing time between trying to start and getting feedback is nowadays
the normal setup for all remote targets as well as for most local tools.
Making that the default for all runs simplifies the code and provides an
opportunity to (a) fix some currently wrong reports of "stopped
immediately" and (b) to remove target-specific (WinRT) or tool-specific
(Valgrind, GammaRay) state members doing essentially the same.
Change-Id: I7f52fee41144188ee8389e922fdc265f8c0a6459
Reviewed-by: David Schulz <david.schulz@qt.io>
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
Diffstat (limited to 'src/plugins/ios/iosruncontrol.cpp')
| -rw-r--r-- | src/plugins/ios/iosruncontrol.cpp | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/src/plugins/ios/iosruncontrol.cpp b/src/plugins/ios/iosruncontrol.cpp index 1699704532..30311f1300 100644 --- a/src/plugins/ios/iosruncontrol.cpp +++ b/src/plugins/ios/iosruncontrol.cpp @@ -64,10 +64,9 @@ void IosRunControl::start() m_runner->start(); } -RunControl::StopResult IosRunControl::stop() +void IosRunControl::stop() { m_runner->stop(); - return StoppedSynchronously; } void IosRunControl::handleRemoteProcessFinished(bool cleanEnd) |