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

Revert "Doc: removed reference to non-existing method"

Browse Source 
This reverts commit 53f0b43a4bfa65ad62bb0c144bab7236ad322b8c.
{QAbstractAnimation::}{updateCurrentValue()} had been modified to
{QVariantAnimation::}{updateCurrentValue()} in a previous patch.

Change-Id: Ibaccf51de816966f16b8f3109e0c20626d5102a8
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
This commit is contained in:
Nico Vertriest 2016-08-24 10:34:44 +02:00
parent d875a04174
commit 6cbd982836
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/corelib/doc/src/animation.qdoc
View File

@ -120,8 +120,10 @@
As mentioned in the previous section, the QPropertyAnimation class can As mentioned in the previous section, the QPropertyAnimation class can
interpolate over Qt properties. It is often this class that should be used interpolate over Qt properties. It is often this class that should be used
for animation of values. Its superclass, QVariantAnimation, does not change for animation of values; in fact, its superclass, QVariantAnimation, has an
any value unless we change it ourselves on the \l{QVariantAnimation::valueChanged()}{valueChanged signal}. 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 A major reason we chose to animate Qt properties is that it
presents us with freedom to animate already existing classes in presents us with freedom to animate already existing classes in