summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNico Vertriest <nico.vertriest@theqtcompany.com>2016-08-22 15:15:15 +0200
committerNico Vertriest <nico.vertriest@theqtcompany.com>2016-08-22 14:20:15 +0000
commit53f0b43a4bfa65ad62bb0c144bab7236ad322b8c (patch)
tree2d7cdbd992ba10ba3230d11737c85a34cc326497
parent4f63051eec8d682584a22a74222ff2d226c9922f (diff)
Doc: removed reference to non-existing method
QAbstractAnimation::updateCurrentValue Change-Id: I1610591ec43d019ca136df5a01350dc6ca7392ff Reviewed-by: Martin Smith <martin.smith@theqtcompany.com>
-rw-r--r--src/corelib/doc/src/animation.qdoc6
1 files changed, 2 insertions, 4 deletions
diff --git a/src/corelib/doc/src/animation.qdoc b/src/corelib/doc/src/animation.qdoc
index 4e71ed4268..4ef6bb5fd8 100644
--- a/src/corelib/doc/src/animation.qdoc
+++ b/src/corelib/doc/src/animation.qdoc
@@ -120,10 +120,8 @@
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; 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}.
+ for animation of values. Its superclass, QVariantAnimation, 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