summaryrefslogtreecommitdiffstats
path: root/tests/auto/qpropertyanimation/tst_qpropertyanimation.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Update current value on QVariantAnimation::setKeyValuesLeonardo Sobral Cunha2009-05-151-0/+34
| | | | | | | The current value was udpated on setKeyValueAt, but not on setKeyValues and this was leading to a semantic inconsistency. Reviewed-by: janarve
* Avoid interpolating if we have less than 2 key values in QVariantAnimationLeonardo Sobral Cunha2009-05-151-0/+31
| | | | | | | If we have less than 2 key values, we should neither try to interpolate nor set the current value. Reviewed-by: janarve
* Indentation and whitespace fixes in animation apiLeonardo Sobral Cunha2009-05-151-2/+2
|
* Addeed a warning if one is trying to animate a property that's not partThierry Bastian2009-05-071-2/+3
| | | | | | of the object Task-number: 251763
* Fixes QPropertyAnimation's default start value update conditionLeonardo Sobral Cunha2009-04-221-0/+22
| | | | | | | The default start value is updated when the animation changes from Stopped to Running state. Reviewed-by: Jan-Arve
* QPropertyAnimation reevaluates the default start value after each runLeonardo Sobral Cunha2009-04-211-5/+5
| | | | | | | | When the start value is not explicitly defined, the property animation will set the default start to be the current property value when updating the animation's state to Running. Reviewed-by: Jan-Arve
* iterationCount becomes loopCount againThierry Bastian2009-04-201-15/+15
|
* Initial import of statemachine branch from the old kinetic repositoryAlexis Menard2009-04-171-0/+831