Details
-
Bug
-
Resolution: Done
-
P1: Critical
-
6.2, 6.3, 6.4, 6.5
-
None
-
f1b1773d0a (qt/qtbase/dev) f1b1773d0a (qt/tqtc-qtbase/dev) 2ebdf562b9 (qt/qtbase/6.4) 14f4801853 (qt/qtbase/6.3) 14f4801853 (qt/tqtc-qtbase/6.3) 2ebdf562b9 (qt/tqtc-qtbase/6.4), 83bfe979c (tqtc/lts-6.2)
Description
If we re-evaluate a property's binding due to a another property's change, and the binding has no further dependencies on any QProperty, then we won't send out a change notification, even when the property now has a different value.
This can happen when the binding captured some mutable state that is not QProperty based (else there would be no way to go from >0 to 0 dependencies).
This is an unintended consequence of the split between binding evaluation and notifications
Attachments
Issue Links
- resulted from
-
QTBUG-104982 [Regression] binding stops being evaluated
- Closed