summaryrefslogtreecommitdiffstats
path: root/tests/auto/qpropertyanimation
Commit message (Collapse)AuthorAgeFilesLines
* Trying to make the animation autotests more robustThierry Bastian2010-02-251-15/+16
| | | | | | Everywhere we have a qWait(duration) followed by a QCOMPARE, there was the risk that it fails because of the test machine being overloaded. So I changed them to QTRY_COMPARE.
* Update copyright year to 2010Jason McDonald2010-01-061-1/+1
| | | | Reviewed-by: Trust Me
* Result API review with JasminThierry Bastian2009-11-041-10/+10
| | | | | | | | | | | | | | | | | QAbstractAnimation: currentTime returns the "complete" current time currentLoopTime() returns the time inside the current loop add setPaused(bool) for consistency with QTimeLine stateChanged: newState passed as first paramater (before oldState) for consistency with the reset of Qt QAnimationGroup: rename clearAnimations to clear rename insertAnimationAt to insertAnimation rename takeAnimationAt to takeAnimation QSequentialAnimationGroup: rename insertPauseAt to insertPause
* Changing the time we wait for the end of the animationThierry Bastian2009-10-281-3/+3
| | | | | We now wait for the animation duration + 100 (instead of 50). It makes tests more reliable on windows (and probably embedded)
* Make the QPropertyAnimation pass on windows by waiting slightly longerThierry Bastian2009-10-281-4/+4
| | | | | Timers on windows are not accurate enough to "only" wait for the animation duration + 50.
* adding autotestsThierry Bastian2009-10-201-0/+14
|
* Animations: updateCurrentTime now receives the currentTime as paramaterThierry Bastian2009-09-281-3/+3
| | | | Reviewed-by: Leo
* Compile testsOlivier Goffart2009-09-241-4/+4
|
* Fix to the autotests of Animations to spit less warningsThierry Bastian2009-09-221-2/+20
|
* animations now display a warning if they don't have a end valueThierry Bastian2009-09-111-0/+5
| | | | also improved the autotests
* Update license headers again.Jason McDonald2009-09-091-4/+4
| | | | Reviewed-by: Trust Me
* Update tech preview license header for files that are new in 4.6.Jason McDonald2009-08-311-13/+13
| | | | Reviewed-by: Trust Me
* QAbstractAnimation: fixes segfault when deleting animation inside ↵Leonardo Sobral Cunha2009-08-271-4/+49
| | | | | | | | | | updateCurrentTime That deletion removed the respective animation from the list of running animations being processed, but not from the copy of the list introduced in 48489988521b818bda8d76e60cb272508e91b490, thus we had a dangling pointer. Reviewed-by: thierry
* animations: make sure setCurrentTime is called on all animationsThierry Bastian2009-08-251-0/+50
| | | | | | | | The problem was we were iterating over the list of running animations. And when calling setCurrentTime(<duration>) on one of them they just unregister themselves from the timer and we would miss some of them. Reviewed-by: leo
* Add autotest to make sure we receive the QVariantAnimation::valueChangedThierry Bastian2009-08-171-0/+28
| | | | Reviewed-by: ogoffart
* Make QPropertyAnimation symetric wrt directionThierry Bastian2009-08-121-0/+42
| | | | | | It is now possible to set a start value and no end value and starting the animation will pick the default end value from the current value of the property that's being animated.
* Update contact URL in license headers.Jason McDonald2009-08-121-1/+1
| | | | Reviewed-by: Trust Me
* QAnimation: fix a jump in values when restarting an animationThierry Bastian2009-07-011-0/+5
|
* Animations: adding an autotest for jumping values when restartingThierry Bastian2009-07-011-0/+52
| | | | | The problem is that when restarting, the time is at the end. So the current value changes to the end value instead of the initial value.
* Update license headers in files that are new in 4.6.Jason McDonald2009-06-171-2/+2
| | | | Reviewed-by: Trust Me
* Fixed a bug in animation when you set a start value that doesn't haveThierry Bastian2009-05-261-19/+58
| | | | | | | | | the same type as the property For example, if you set a start value of 0 (integer) for a qreal animation, it would not work. Reviewed-by: janarve
* 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-172-0/+836
generated by cgit v0.12 at 2024-12-27 07:51:05 (GMT)