QProperty: Fix notification logic for eager properties

This ensurse that we do not do dobule notifications in setValue.
Moerover we avoid needless notifications in markDirtyAndNotifyObservers
when the value did not change. Lastly, if the value did actually change,
we pass that information along to notify, so that we do not evaluate the
eager property twice.
Fixes a test-case which errorneously relied on the old behavior, and
adds a new test which verifies that the fix works.

Change-Id: I8ec6fa2fe8611565dfc603ceab3ba5f92999b26c
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>

1 files changed, 5 insertions, 2 deletions

diff --git a/src/corelib/kernel/qproperty.cpp b/src/corelib/kernel/qproperty.cpp
index 103c3d8482..147103aed9 100644
--- a/src/corelib/kernel/qproperty.cpp
+++ b/src/corelib/kernel/qproperty.cpp
@@ -110,12 +110,15 @@ void QPropertyBindingPrivate::markDirtyAndNotifyObservers()
 
     eagerlyUpdating = true;
     QScopeGuard guard([&](){eagerlyUpdating = false;});
+    bool knownIfChanged = false;
     if (requiresEagerEvaluation()) {
         // these are compat properties that we will need to evaluate eagerly
-        evaluateIfDirtyAndReturnTrueIfValueChanged(propertyDataPtr);
+        if (!evaluateIfDirtyAndReturnTrueIfValueChanged(propertyDataPtr))
+            return;
+        knownIfChanged = true;
     }
     if (firstObserver)
-        firstObserver.notify(this, propertyDataPtr);
+        firstObserver.notify(this, propertyDataPtr, knownIfChanged);
     if (hasStaticObserver)
         staticObserverCallback(propertyDataPtr);
 }