ProjectExplorer: Streamline OutputFormatter creation a bit

Note that the concept of a single monolithic OutputFormatter per
RunConfiguration (and why RunConfiguration, not RunControl to start
with?) is unchanged and suboptimal as one cannot easily combine
existing use cases, e.g. Python_and_Qt.

Change-Id: Ibeb8191020387324f22ed313230293597f96e36a
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
This commit is contained in:
hjk
2018-04-06 09:21:44 +02:00
parent 845541c89d
commit 83c6a4916c
19 changed files with 26 additions and 63 deletions

View File

@@ -48,6 +48,7 @@ const char postFinishShellCmdsKey[] = "Android.PostFinishShellCmdListKey";
AndroidRunConfiguration::AndroidRunConfiguration(Target *target, Core::Id id)
: RunConfiguration(target, id)
{
setOutputFormatter<QtSupport::QtOutputFormatter>();
}
void AndroidRunConfiguration::setPreStartShellCommands(const QStringList &cmdList)
@@ -80,11 +81,6 @@ QWidget *AndroidRunConfiguration::createConfigurationWidget()
return configWidget;
}
Utils::OutputFormatter *AndroidRunConfiguration::createOutputFormatter() const
{
return new QtSupport::QtOutputFormatter(target()->project());
}
bool AndroidRunConfiguration::fromMap(const QVariantMap &map)
{
if (!RunConfiguration::fromMap(map))