summaryrefslogtreecommitdiffstats
path: root/examples/declarative/animations
Commit message (Collapse)AuthorAgeFilesLines
* Make "on" syntax mandatory for value sources and interceptorsAaron Kennedy2010-03-022-6/+6
| | | | | | | | | | | | | | | | | | | | | 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.
* Renamed Flickable viewportXXX properties contentXXXMartin Jones2010-02-261-1/+1
| | | | A viewport is the thing you look through, not what you look at.
* Updates all qml examples/demos to use the easing curve value type syntaxLeonardo Sobral Cunha2010-02-232-47/+47
|
* Rename MouseRegion -> MouseAreaMartin Jones2010-02-221-1/+1
|
* Get rid of the matchProperties/properties distinction, as itMichael Brasser2010-02-181-2/+2
| | | | | | | | | | | 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.
* Removed "running: true" for animations used as propertyvaluesourceLeonardo Sobral Cunha2010-02-112-6/+6
| | | | | | This attribution is not necessary anymore since 923710196d6d5..., Reviewed-by: Michael Brasser
* Rename targets -> matchTargets and properties -> matchProperties.Michael Brasser2009-11-061-2/+2
|
* more autotestsYann Bodson2009-11-041-4/+1
|
* cleanupYann Bodson2009-10-308-0/+236