forked from qt-creator/qt-creator
QmlDebug: Simplify error and state signaling
There is no point in sending two signals for every state change and error. Also, the signals only reflect events in the socket, not in the logical connection. Change-Id: I617a925c69164aa1a02a7781b9da7dca55daa304 Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>
This commit is contained in:
@@ -34,7 +34,6 @@
|
||||
#include <debugger/debuggerengine.h>
|
||||
|
||||
#include <qmldebug/qdebugmessageclient.h>
|
||||
#include <qmldebug/qmldebugclient.h>
|
||||
#include <qmldebug/qmloutputparser.h>
|
||||
#include <qmljs/iscriptevaluator.h>
|
||||
#include <qmljs/qmljsdocument.h>
|
||||
@@ -142,11 +141,12 @@ private:
|
||||
void startApplicationLauncher();
|
||||
void stopApplicationLauncher();
|
||||
|
||||
void connectionErrorOccurred(QDebugSupport::Error socketError);
|
||||
void connectionErrorOccurred(QAbstractSocket::SocketError socketError);
|
||||
void connectionStateChanged(QAbstractSocket::SocketState socketState);
|
||||
|
||||
void clientStateChanged(QmlDebug::QmlDebugClient::State state);
|
||||
void checkConnectionState();
|
||||
void showConnectionStateMessage(const QString &message);
|
||||
void showConnectionErrorMessage(const QString &message);
|
||||
bool isConnected() const;
|
||||
|
||||
private:
|
||||
|
||||
Reference in New Issue
Block a user