0 Replies Latest reply on Dec 9, 2009 9:32 PM by Chet Haase

    [svn:fx-trunk] 12769: Workaround for player issue.

    Chet Haase Level 3

      Revision: 12769

      Revision: 12769

      Author:   chaase@adobe.com

      Date:     2009-12-09 21:31:49 -0800 (Wed, 09 Dec 2009)

      Log Message:

      ***********

      Workaround for player issue. The bounds used internally by the player do not match the bounds returned from getBounds(), so it is tough to create a bitmap snapshot of a component that has the same location/bounds as the player would use. This makes it problematic to use bitmaps with ShaderFilter to substitute for the real object, and causes some objects to shift during the effects (Wipe, CrossFade, AnimateTransitionShader). This is particularly true for objects with filtered children (where the filters run outside the bounds of the parent) and objects with text areas that border the left/top of the component. The workaround is to draw the object into a bitmap with an opaque background and measure the resulting colored pixels with BitmapData.getColorBoundsRect() to get the true bounds as seen by the player.

       

      Also changed some FIXME comments to TODOs in ScrollBarBase, as those comments were more about future work than must-fix items in Flex 4.

       

      QE notes: No

      Doc notes: No

      Bugs: SDK-20250

      Reviewer: Jason

      Tests run: checkintests, Mustella spark/effects/AnimateTransitionShader|CrossFade|Wipe

      Is noteworthy for integration: No

       

      Ticket Links:

      ***********

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

       

      Modified Paths:

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

          flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/ScrollBarBas e.as

          flex/sdk/trunk/frameworks/projects/spark/src/spark/utils/BitmapUtil.as