From cc4bf69d6799fba9e8acb3945c3ffe45ffabab88 Mon Sep 17 00:00:00 2001 From: Jarek Kobus Date: Wed, 19 Feb 2025 17:32:47 +0100 Subject: [PATCH] Valgrind: Simplify the popping code It looks like runControl()->showOutputPane() is a good equivalent to the hack with an introspection of the AppOutputPane object. Change-Id: I6c4fe3bf2a797eac9ac454140bf78bb2eb278129 Reviewed-by: hjk --- src/plugins/valgrind/valgrindengine.cpp | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/src/plugins/valgrind/valgrindengine.cpp b/src/plugins/valgrind/valgrindengine.cpp index 39878fb9770..1ab2ae4bc41 100644 --- a/src/plugins/valgrind/valgrindengine.cpp +++ b/src/plugins/valgrind/valgrindengine.cpp @@ -7,12 +7,9 @@ #include "valgrindtr.h" #include -#include #include #include -#include - #include #include #include @@ -140,10 +137,7 @@ void ValgrindToolRunner::receiveProcessError(const QString &errorString, Process default: break; } - - QObject *obj = ExtensionSystem::PluginManager::getObjectByName("AppOutputPane"); - if (auto pane = qobject_cast(obj)) - pane->popup(IOutputPane::NoModeSwitch); + runControl()->showOutputPane(); } } // Valgrid::Internal