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, 3 insertions, 3 deletions

diff --git a/tests/auto/declarative/visual/animation/parallelAnimation/parallelAnimation.qml b/tests/auto/declarative/visual/animation/parallelAnimation/parallelAnimation.qml
index 9e0422f..7021e05 100644
--- a/tests/auto/declarative/visual/animation/parallelAnimation/parallelAnimation.qml
+++ b/tests/auto/declarative/visual/animation/parallelAnimation/parallelAnimation.qml
@@ -34,10 +34,10 @@ Rectangle {
     }
 
     transitions: Transition {
-        PropertyAnimation { matchTargets: redRect; matchProperties: "x,color"; duration: 300 }
+        PropertyAnimation { targets: redRect; properties: "x,color"; duration: 300 }
         ParallelAnimation {
-            NumberAnimation { matchTargets: redRect2; matchProperties: "x"; duration: 300 }
-            ColorAnimation { matchTargets: redRect2; matchProperties: "color"; duration: 300 }
+            NumberAnimation { targets: redRect2; properties: "x"; duration: 300 }
+            ColorAnimation { targets: redRect2; properties: "color"; duration: 300 }
         }
     }
 }