Doc: Be transparent about what type of entity qmlobject_connect is
Both things are not methods, and of course can not be used as such. Change-Id: Iadaa0841ff627ad6705c66f50e7ee57aa93fb042 Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
This commit is contained in:
parent
82f6e02e52
commit
94d68a9410
|
@ -49,7 +49,7 @@ T qmlGetConfigOption(const char *var)
|
|||
Connect \a Signal of \a Sender to \a Method of \a Receiver. \a Signal must be
|
||||
of type \a SenderType and \a Receiver of type \a ReceiverType.
|
||||
|
||||
Unlike QObject::connect(), this method caches the lookup of the signal and method
|
||||
Unlike QObject::connect(), this macro caches the lookup of the signal and method
|
||||
indexes. It also does not require lazy QMetaObjects to be built so should be
|
||||
preferred in all QML code that might interact with QML built objects.
|
||||
|
||||
|
@ -88,7 +88,7 @@ do { \
|
|||
Disconnect \a Signal of \a Sender from \a Method of \a Receiver. \a Signal must be
|
||||
of type \a SenderType and \a Receiver of type \a ReceiverType.
|
||||
|
||||
Unlike QObject::disconnect(), this method caches the lookup of the signal and method
|
||||
Unlike QObject::disconnect(), this macro caches the lookup of the signal and method
|
||||
indexes. It also does not require lazy QMetaObjects to be built so should be
|
||||
preferred in all QML code that might interact with QML built objects.
|
||||
|
||||
|
|
Loading…
Reference in New Issue