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>

1 files changed, 3 insertions, 2 deletions

diff --git a/src/plugins/qmlprofiler/qmlprofilerclientmanager.h b/src/plugins/qmlprofiler/qmlprofilerclientmanager.h
index 0cbf88dc56..9eae3e0cad 100644
--- a/src/plugins/qmlprofiler/qmlprofilerclientmanager.h
+++ b/src/plugins/qmlprofiler/qmlprofilerclientmanager.h
@@ -33,10 +33,10 @@
 
 #include "qmlprofilerstatemanager.h"
 #include <qmldebug/qmlprofilereventlocation.h>
-#include <qmldebug/qmldebugclient.h>
 
 #include <QObject>
 #include <QStringList>
+#include <QAbstractSocket>
 
 namespace QmlProfiler {
 class QmlProfilerModelManager;
@@ -72,7 +72,8 @@ private slots:
     void tryToConnect();
     void qmlDebugConnectionOpened();
     void qmlDebugConnectionClosed();
-    void qmlDebugConnectionError(QDebugSupport::Error error);
+    void qmlDebugConnectionError(QAbstractSocket::SocketError error);
+    void qmlDebugConnectionStateChanged(QAbstractSocket::SocketState state);
     void logState(const QString &);
 
     void retryMessageBoxFinished(int result);