forked from qt-creator/qt-creator
Qnx: Add support for qml profiler in BlackBerry/Qnx
We cannot set -qmljsdebugger arg in bar-descriptor.xml file since it can be done in DeployStep only. QTC architecture do not allows this. Current approach modifies already deployed MANIFEST.MF on the device. This patch has nothing to do with QML analyzer for pure QNX, it's purely for BlackBerry. Task-number: QTCREATORBUG-10520 Change-Id: I89e83c6ff70a7a35344ff7e3fe573fc19e797ccb Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
This commit is contained in:
committed by
Fanda Vacek
parent
1910fe9175
commit
2c732970b8
@@ -240,8 +240,6 @@ void QmlProfilerClientManager::connectToClient()
|
||||
if (!d->connection || d->connection->state() != QAbstractSocket::UnconnectedState)
|
||||
return;
|
||||
|
||||
QmlProfilerTool::logStatus(QString::fromLatin1("QML Profiler: Connecting to %1:%2 ...")
|
||||
.arg(d->tcpHost, QString::number(d->tcpPort)));
|
||||
d->connection->connectToHost(d->tcpHost, d->tcpPort);
|
||||
}
|
||||
|
||||
@@ -309,14 +307,17 @@ void QmlProfilerClientManager::connectionStateChanged()
|
||||
case QAbstractSocket::ConnectingState: {
|
||||
if (QmlProfilerPlugin::debugOutput)
|
||||
qWarning("QML Profiler: Connecting to debug server ...");
|
||||
QmlProfilerTool::logStatus(tr("QML Profiler: Connecting to %1:%2 ...")
|
||||
.arg(d->tcpHost, QString::number(d->tcpPort)));
|
||||
break;
|
||||
}
|
||||
case QAbstractSocket::ConnectedState:
|
||||
{
|
||||
if (QmlProfilerPlugin::debugOutput)
|
||||
qWarning("QML Profiler: connected and running");
|
||||
// notify the client recording status
|
||||
clientRecordingChanged();
|
||||
// notify the client recording status
|
||||
clientRecordingChanged();
|
||||
QmlProfilerTool::logStatus(tr("QML Profiler: connected and running"));
|
||||
break;
|
||||
}
|
||||
case QAbstractSocket::ClosingState:
|
||||
|
||||
Reference in New Issue
Block a user