Get rid of the matchProperties/properties distinction, as it

has proven to be confusing in practice.

property/target and properties/targets will be functionally equivilant
(the only distinction being singular/plural). In a transition these
properties can be used for both 'matching' and explicit animation
based on whether a 'to' value is supplied.

The documentation, tests, examples and demos have been updated as well.

1 files changed, 24 insertions, 0 deletions

diff --git a/tests/auto/declarative/visual/animation/loop/loop.qml b/tests/auto/declarative/visual/animation/loop/loop.qml
new file mode 100644
index 0000000..f6049ae
--- /dev/null
+++ b/tests/auto/declarative/visual/animation/loop/loop.qml
@@ -0,0 +1,24 @@
+import Qt 4.6
+
+Rectangle {
+    id: wrapper
+    width: 600
+    height: 100
+
+    Rectangle {
+        id: redRect
+        width: 100; height: 100
+        color: Qt.rgba(1,0,0)
+        /* This should produce an animation that starts at 0, animates smoothly
+           to 100, jumps to 200, animates smoothly to 400, animates smoothly
+           back to 100, jumps to 200, and so on.
+        */
+        x: SequentialAnimation {
+            repeat: true
+            NumberAnimation { to: 100; duration: 1000 }
+            NumberAnimation { from: 200; to: 400; duration: 1000 }
+        }
+
+    }
+
+}