diff options
| author | hjk <hjk@qt.io> | 2017-06-27 17:30:32 +0200 |
|---|---|---|
| committer | hjk <hjk@qt.io> | 2017-06-28 09:05:43 +0000 |
| commit | 682cd36b1598c29a17b993ba94fa006a012aa796 (patch) | |
| tree | 85eab1aad935bd44331069f6fddb6d80603c16a5 /src/plugins/valgrind/valgrindengine.cpp | |
| parent | 228e4a7542f03acde52c697dcbd3d4d93efa3cf5 (diff) | |
Valgrind: Remove starting() signal
It's only used internally as one-time communication between
worker and the *Tool singleton that handles toolbar button
states.
We basically start immediately after creation of the worker, so
any pre-start tool bar specific operations can be done at
RunWorker creation time.
Medium term, the runworker should proably steer "their" buttons
more directly.
Change-Id: Id6df703746ece5eebc23507739cd2a92ec55d11d
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Diffstat (limited to 'src/plugins/valgrind/valgrindengine.cpp')
| -rw-r--r-- | src/plugins/valgrind/valgrindengine.cpp | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/src/plugins/valgrind/valgrindengine.cpp b/src/plugins/valgrind/valgrindengine.cpp index 55365f7be1..649a1d7594 100644 --- a/src/plugins/valgrind/valgrindengine.cpp +++ b/src/plugins/valgrind/valgrindengine.cpp @@ -66,7 +66,6 @@ ValgrindToolRunner::ValgrindToolRunner(RunControl *runControl) void ValgrindToolRunner::start() { - emit starting(); FutureProgress *fp = ProgressManager::addTimedTask(m_progress, progressTitle(), "valgrind", 100); fp->setKeepOnFinish(FutureProgress::HideOnFinish); connect(fp, &FutureProgress::canceled, |