0 Replies Latest reply on Nov 11, 2009 9:21 AM by rfrishbe

    [svn:fx-trunk] 11656: Fixing a bug in the Flash Component Kit for the Flex Component Templates for Flash .

    rfrishbe Level 3

      Revision: 11656

      Author:   rfrishbe@adobe.com

      Date:     2009-11-11 09:20:44 -0800 (Wed, 11 Nov 2009)

       

      Log Message:

      ***********

      Fixing a bug in the Flash Component Kit for the Flex Component Templates for Flash.  The issue is around how we refactored the autoUpdateCurrentState flag and the first time we detect the currentState.  Before we would check the currentLabel on every enterFrame, but now we only do it when autoUpdateCurrentState is set.  In order to match what we were doing before, we decided to add that check in the constructor so the state gets set initially.

       

      However, this isn?\226?\128?\153t exactly the behavior we had before, and using the Flex Component Templates for Flash, there?\226?\128?\153s a race condition.  When the skin loads up, the component will set the currentState on the UIMovieClip.  However, because we set _currentState in the constructor, the currentState setter short-circuits.  The problem with this is that now goToAndStop() isn?\226?\128?\153t called on the frame and the script continues to run.

       

      For the fix, we delay the first time we set up _currentState for an enterFrame, which matches the behavior in 3.4.

       

      QE notes: -

      Doc notes: -

      Bugs: SDK-24147

      Reviewer: Glenn

      Tests run: checkintest, mustella FCK

      Is noteworthy for integration: No

       

      Ticket Links:

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

          http://bugs.adobe.com/jira/browse/SDK-24147

       

      Modified Paths:

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

          flex/sdk/trunk/frameworks/projects/flash-integration/src/mx/flash/UIMovieClip.as