Fixed custom code related to connectNotify behaviour.

The code injection that deals with calling connectNotify in the
binding generated with the protected hack turned off should call
the connectNotify method directly instead of using the protected
caller.

Reviewed by Renato Araújo <renato.filho@openbossa.org>
Reviewed by Luciano Wolf <luciano.wolf@openbossa.org>

1 files changed, 3 insertions, 3 deletions

diff --git a/PySide/QtCore/glue/qobject_connect.cpp b/PySide/QtCore/glue/qobject_connect.cpp
index 698b3c8dd..5b6f2547d 100644
--- a/PySide/QtCore/glue/qobject_connect.cpp
+++ b/PySide/QtCore/glue/qobject_connect.cpp
@@ -72,12 +72,12 @@ static bool qobjectConnectCallback(QObject* source, const char* signal, PyObject
         slotIndex = metaObject->indexOfSlot(slot);
     }
     if (QMetaObject::connect(source, signalIndex, receiver, slotIndex, type)) {
-        // FIXME: Need to cast to QObjectWrapper* and call the public version of connectNotify
-        //        when avoiding the protected hack.
         #ifndef AVOID_PROTECTED_HACK
             source->connectNotify(signal);
         #else
-            reinterpret_cast<QObjectWrapper*>(source)->connectNotify_protected(signal);
+            // Need to cast to QObjectWrapper* and call the public version of
+            // connectNotify when avoiding the protected hack.
+            reinterpret_cast<QObjectWrapper*>(source)->connectNotify(signal);
         #endif
         if (usingGlobalReceiver)
             signalManager.globalReceiverConnectNotify(source, slotIndex);