From ba9825625d3340dba1e17efb4629b65bb575df3e Mon Sep 17 00:00:00 2001
From: Ulf Hermann <ulf.hermann@qt.io>
Date: Fri, 15 Jul 2016 13:09:38 +0200
Subject: QmlDebug: Decouple log messages from connection failures

A socket error is not the only possible reason for a connection failure
and exposing socket error codes to the upper layers is unnecessary.

Change-Id: I27e9f21160ecea5b0d811b83b7ab0ab9071cacff
Reviewed-by: hjk <hjk@qt.io>
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
---
 src/plugins/qmlprofiler/qmlprofilerclientmanager.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'src/plugins/qmlprofiler/qmlprofilerclientmanager.h')

diff --git a/src/plugins/qmlprofiler/qmlprofilerclientmanager.h b/src/plugins/qmlprofiler/qmlprofilerclientmanager.h
index 1b4b71ed2c..c4a478d9c7 100644
--- a/src/plugins/qmlprofiler/qmlprofilerclientmanager.h
+++ b/src/plugins/qmlprofiler/qmlprofilerclientmanager.h
@@ -72,8 +72,8 @@ private slots:
     void tryToConnect();
     void qmlDebugConnectionOpened();
     void qmlDebugConnectionClosed();
-    void qmlDebugConnectionError(QAbstractSocket::SocketError error);
-    void qmlDebugConnectionStateChanged(QAbstractSocket::SocketState state);
+    void qmlDebugConnectionFailed();
+
     void logState(const QString &);
 
     void qmlComplete(qint64 maximumTime);
-- 
cgit v1.2.1