0 Replies Latest reply on Apr 16, 2010 4:14 PM by Chet Haase

    [svn:fx-trunk] 15526: Two effects fixes, one states/SetProperty fix.

    Chet Haase Level 3

      Revision: 15526

      Revision: 15526

      Author:   chaase@adobe.com

      Date:     2010-04-16 16:14:38 -0700 (Fri, 16 Apr 2010)

      Log Message:


      Two effects fixes, one states/SetProperty fix.

      The Fade fix allows objects which don't exist in the next state, but which don't have valid values set in that state for position/orientation, to fade out in place.

      The states fix cleans up the layout constraint docs in UIComponent and fixes logic in SetProperty that makes it possible to actually unset these properties in MXML.

      The AnimateTransform fix cleans up logic when using AnimateTransform directly to auto-animate properties that change between states.


      QE notes: Fade_accessor Fade_relevantProperties_Default fails because the affectedProperties of Fade has changed with one of these fixes. The test needs to be updated.

      Doc notes: None

      Bugs: sdk-25389, sdk-24989, sdk-24925

      Reviewer: Corey (UIComponent, SetProperty) and Jason (the rest)

      Tests run: checkintests, Mustella spark/effects, mx/states

      Is noteworthy for integration: yes: downstream tools wanted fix for sdk-24925


      Ticket Links:







      Modified Paths:






          flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/supportClasses/AnimateTransfor mInstance.as