0 Replies Latest reply on Nov 5, 2009 3:00 PM by Chet Haase

    [svn:fx-trunk] 11481: Fixed a glitch in my Fade fix/refactoring yesterday.

    Chet Haase Level 3

      Revision: 11481

      Author:   chaase@adobe.com

      Date:     2009-11-05 15:00:07 -0800 (Thu, 05 Nov 2009)

       

      Log Message:

      ***********

      Fixed a glitch in my Fade fix/refactoring yesterday. When a fade-in had a startDelay where the target object was not starting with a 0 alpha (like if it had alpha=1, but was going from not visible to visible or not-parented to parented), then Fade would fail to assign a 0 alpha to the object before it began the startDelay. This has the effect of making the object blink in at the beginning of the startDelay (because we made the object visible but opaque), then blink out at the end of the startDelay and fade in from there. The fix was to, like the old FadeInstance logic, set the target alpha to 0 if that's the alpha that we will start from in the actual effect.

       

      QE notes: None.

      Doc notes: None.

      Bugs: none

      Reviewer: Kevin

      Tests run: checkintests, Mustella spark/effects/Fade

      Is noteworthy for integration: yes - it's a fix for a  problem in a 'noteworthy' fix from commit 11447 for bug sdk-23399, which was requested by downstream teams.

       

      Ticket Links:

      ************

          http://bugs.adobe.com/jira/browse/sdk-23399

       

      Modified Paths:

      **************

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