| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
On macos (as on symbian), we need to leave some time for the
application to become responsive.
|
|
|
|
|
|
|
| |
There were cases (now covered by autotests) where the state of the
animations could be wrong.
Reviewed-by: janarve
|
|
|
|
|
|
|
|
| |
The animation was not starting in time, as events from Symbian app
start up had not had time to be flushed through. The addition of a 1s
QTest::qWait gives plenty of time for the app to settle.
Reviewed-by: Janne Anttila
|
| |
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
|
|
|
|
|
| |
If you resumed a parallel animation group, it would always restart
(ie. stop and start) the animation which would reset its current time
to 0 and trigger flickering.
autotest included.
Task-Number: 259102
|
| |
|
|
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
|