1berry/qtbase
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Doc: Update docs to reflect method being renamed

Browse Source 
The new method has been renamed from markDirty to notify.

Fixes: QTBUG-111267
Change-Id: Ib7926a315cfd11ca6930c785290089b7031d34ff
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
(cherry picked from commit 12c62dd243dd139023fa1fc5c3a7c0fd8e3ee0ba)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
This commit is contained in:
Andreas Eliasson 2023-03-07 13:47:06 +01:00 committed by Qt Cherry-pick Bot
parent ec3aac74a4
commit 2828b3fdca
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/corelib/doc/snippets/code/src_corelib_kernel_qproperty.cpp
View File

@ -144,7 +144,7 @@ public:
Q_D(MyClass);
d->clients.push_back(c);
// notify that the value could have changed
d->hasClientsData.markDirty();
d->hasClientsData.notify();
}
private:
Q_DECLARE_PRIVATE(MyClass)

6
src/corelib/kernel/qproperty.cpp
View File

@ -1659,13 +1659,13 @@ QString QPropertyBindingError::description() const
have changed. Whenever a bindable property used in the callback changes,
this happens automatically. If the result of the callback might change
because of a change in a value which is not a bindable property,
it is the developer's responsibility to call markDirty
it is the developer's responsibility to call \c notify
on the QObjectComputedProperty object.
This will inform dependent properties about the potential change.
Note that calling markDirty might trigger change handlers in dependent
Note that calling \c notify might trigger change handlers in dependent
properties, which might in turn use the object the QObjectComputedProperty
is a member of. So markDirty must not be called when in a transitional
is a member of. So \c notify must not be called when in a transitional
or invalid state.
QObjectComputedProperty is not suitable for use with a computation that depends