Remove not needed invokeMethod() calls when emitting finished() signal

Internally the transfer reply starts via QueuedConnection. Therefore the
finished signal doesn't have to be delayed even further. In addition
document the tight restriction when being interested in signals from
QBluetoothtransferReply.

Change-Id: I0358140e96e1e9709158310c493f34ea5e40582a
Reviewed-by: Timur Pocheptsov <Timur.Pocheptsov@digia.com>
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>

1 files changed, 2 insertions, 2 deletions

diff --git a/src/bluetooth/qbluetoothtransferreply_qnx.cpp b/src/bluetooth/qbluetoothtransferreply_qnx.cpp
index acd60894..4c378065 100644
--- a/src/bluetooth/qbluetoothtransferreply_qnx.cpp
+++ b/src/bluetooth/qbluetoothtransferreply_qnx.cpp
@@ -137,7 +137,7 @@ bool QBluetoothTransferReplyQnx::start()
             m_finished = true;
             m_running = false;
             emit QBluetoothTransferReply::error(m_error);
-            QMetaObject::invokeMethod(this, "finished", Qt::QueuedConnection, Q_ARG(QBluetoothTransferReply*, this));
+            emit finished(this);
             return false;
         }
         if (request().address().isNull()) {
@@ -146,7 +146,7 @@ bool QBluetoothTransferReplyQnx::start()
             m_finished = true;
             m_running = false;
             emit QBluetoothTransferReply::error(m_error);
-            QMetaObject::invokeMethod(this, "finished", Qt::QueuedConnection, Q_ARG(QBluetoothTransferReply*, this));
+            emit finished(this);
             return false;
         }
         startOPP(file->fileName());