diff options
authorNico Vertriest <>2016-08-24 10:34:44 +0200
committerNico Vertriest <>2016-08-26 11:40:11 +0000
commit6cbd982836266a59e926d8f149ad0013bd8162a3 (patch)
parentd875a0417417d1921e5a4f967d6aff72edef71c7 (diff)
Revert "Doc: removed reference to non-existing method"
This reverts commit 53f0b43a4bfa65ad62bb0c144bab7236ad322b8c. {QAbstractAnimation::}{updateCurrentValue()} had been modified to {QVariantAnimation::}{updateCurrentValue()} in a previous patch. Change-Id: Ibaccf51de816966f16b8f3109e0c20626d5102a8 Reviewed-by: Friedemann Kleint <> Reviewed-by: Thiago Macieira <>
1 files changed, 4 insertions, 2 deletions
diff --git a/src/corelib/doc/src/animation.qdoc b/src/corelib/doc/src/animation.qdoc
index 4ef6bb5fd8..4e71ed4268 100644
--- a/src/corelib/doc/src/animation.qdoc
+++ b/src/corelib/doc/src/animation.qdoc
@@ -120,8 +120,10 @@
As mentioned in the previous section, the QPropertyAnimation class can
interpolate over Qt properties. It is often this class that should be used
- for animation of values. Its superclass, QVariantAnimation, does not change
- any value unless we change it ourselves on the \l{QVariantAnimation::valueChanged()}{valueChanged signal}.
+ for animation of values; in fact, its superclass, QVariantAnimation, has an
+ empty implementation of \l{QAbstractAnimation::}{updateCurrentValue()}, and
+ does not change any value unless we change it ourselves on the
+ \l{QVariantAnimation::valueChanged()}{valueChanged signal}.
A major reason we chose to animate Qt properties is that it
presents us with freedom to animate already existing classes in