Avoid accessing QObjectPrivate::currentSender directly from QtDBus
In particular, currentSender->signal is about to be changed from the method index range to the signal index range (i.e., excluding non-signal methods). The public senderSignalIndex() function will still return the index in the method range, so QtDBus will then continue to work without change. If necessary, QtDBus can afterwards be ported back to using the internal API again (including the new QMetaObjectPrivate API for working with methods in the signal range). Change-Id: I58212e859560a8e241adee99dd2da9ef009d4e5b Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> Reviewed-by: Olivier Goffart <ogoffart@woboq.com>bb10
parent
cd95bcd7db
commit
b60f6447d0
|
|
@ -277,8 +277,7 @@ void QDBusAdaptorConnector::polish()
|
|||
|
||||
void QDBusAdaptorConnector::relaySlot(void **argv)
|
||||
{
|
||||
QObjectPrivate *d = static_cast<QObjectPrivate *>(d_ptr.data());
|
||||
relay(d->currentSender->sender, d->currentSender->signal, argv);
|
||||
relay(sender(), senderSignalIndex(), argv);
|
||||
}
|
||||
|
||||
void QDBusAdaptorConnector::relay(QObject *senderObj, int lastSignalIdx, void **argv)
|
||||
|
|
|
|||
Loading…
Reference in New Issue