feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

Make ApplicationLauncher report QStrings, not QByteArray

Browse Source 
Realistically, we only have UTF-8/plain ASCII messages, and if not then
the conversion should happen when the message enters the "creator eco
system" as there's potentially information on the actual encoding
present, not at some random consumer further down the chain.

Change-Id: Ie21199b99255f5c4d28fce3da7db2fd6c3bcfb3a
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
This commit is contained in:
hjk
2017-07-13 17:59:53 +02:00
parent 77e32885a7
commit 6a44992050
7 changed files with 28 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/plugins/projectexplorer/runconfiguration.cpp
View File

@@ -1309,13 +1309,13 @@ void SimpleTargetRunner::start()
});
connect(&m_launcher, &ApplicationLauncher::remoteStderr,
this, [this](const QByteArray &output) {
appendMessage(QString::fromUtf8(output), Utils::StdErrFormatSameLine);
this, [this](const QString &output) {
appendMessage(output, Utils::StdErrFormatSameLine);
});
connect(&m_launcher, &ApplicationLauncher::remoteStdout,
this, [this](const QByteArray &output) {
appendMessage(QString::fromUtf8(output), Utils::StdOutFormatSameLine);
this, [this](const QString &output) {
appendMessage(output, Utils::StdOutFormatSameLine);
});
connect(&m_launcher, &ApplicationLauncher::finished,