| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Task-number: QTBUG-13799
Reviewed-by: Martin Jones
|
|
|
|
|
|
|
| |
We need to clear the data from the last run if the animation doesn't
match any of the state actions (or if there are no actions).
Task-number: QTBUG-12805
|
|
|
|
|
|
|
|
|
|
|
|
| |
SpringFollow was turned into SpringAnimation so it could be
used inside a Behavior. This patch completes the work and makes
it usable inside a transition.
This is the documented behavior of SpringAnimation, the patch
is essential to make SpringAnimation work consistently.
Reviewed-by: Michael Brasser
Task-number: QTBUG-12141
|
|
|
|
| |
Task-number: QTBUG-11853
|
|
|
|
|
| |
If the animation had an explicit "running: true", the animation would
be registered with the engine twice, which prevented a proper start.
|
|
|
|
|
| |
Task-number:
Reviewed-by: Martin Jones
|
|
|
|
|
| |
Task-number: QTBUG-9491
Reviewed-by: Martin Jones
|
|
|
|
|
|
|
| |
QDeclarativeItem will be public, all properties that are relaying on
private types must be private too.
Reviewed-by:akennedy
|
|
|
|
|
|
| |
Since we aren't releasing for 4.6, all types are new in 4.7.
Task-number: QTBUG-10081
|
|
|
|
| |
QTBUG-9726
|
|
|
|
|
| |
Task-number:
Reviewed-by: Martin Jones
|
| |
|
|
|
|
|
| |
Too misleading to have on the Qt object, as it only means infinite
for animation loops.
|
|
|
|
|
| |
You can now loop a fixed number of times as well as forever. The old
repeat behavior (loop forever) can be acheived with loops: Qt.Infinite.
|
|
|
|
|
|
| |
Shortest as default too often led to unintuitive behavior. For example,
RotationAnimation { from: 0; to: 360 } will not animate at all. Numerical
gives the least surprising results.
|
|
|
|
| |
This was probably a bug in the test data.
|
|
|
|
| |
Task-number: QTBUG-8613
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Where you would have written
x: NumberAnimation {}
y: Behavior {}
you now must write
NumberAnimation on x {}
Behavior on y {}
This change also makes the parser more strict with respect to multiple
assignments to a single property - they're no longer allowed. For example
this
x: 10
x: 11
is now an error.
|
|
|
|
| |
to QDeclarativeXXX.
|
|
QDeclarativeXXX.
|