Permit signals to be emitted in a different thread

The QQmlNotifier approach to connecting to signals did not
support the cross-thread signal/slot model used elsewhere in
Qt.  This change allows one specific case of that - emitting
a signal in a different thread than the one the QObject
lives - to work.

Task-number: QTBUG-25647
Change-Id: Ia8fdaf4c7d7e2ccd7ff7657bb1d8e26277eb60aa
Reviewed-by: Aaron Kennedy <aaron.kennedy@nokia.com>

1 files changed, 2 insertions, 2 deletions

diff --git a/src/qml/qml/qqmlboundsignal.cpp b/src/qml/qml/qqmlboundsignal.cpp
index 358e945d41..8b3a39c12e 100644
--- a/src/qml/qml/qqmlboundsignal.cpp
+++ b/src/qml/qml/qqmlboundsignal.cpp
@@ -221,14 +221,14 @@ void QQmlAbstractBoundSignal::removeFromObject()
 }
 
 QQmlBoundSignal::QQmlBoundSignal(QObject *scope, const QMetaMethod &signal,
-                               QObject *owner)
+                               QObject *owner, QQmlEngine *engine)
 : m_expression(0), m_params(0), m_scope(scope), m_index(signal.methodIndex())
 {
     setParamsValid(false);
     setIsEvaluating(false);
     addToObject(owner);
     callback = &subscriptionCallback;
-    QQmlNotifierEndpoint::connect(scope, m_index);
+    QQmlNotifierEndpoint::connect(scope, m_index, engine);
 }
 
 QQmlBoundSignal::~QQmlBoundSignal()