The bitmap data representing the start state of this effect. If this property is not set, it is calculated automatically when the effect is played by taking a snapshot of the target object, or by using a transparent bitmap if the object does not exist in the start view state of a transition.

The bitmap data representing the end state of this effect. If this property is not set, it is calculated automatically when the effect is played by taking a snapshot of the target object, or by using a transparent bitmap if the object does not exist in the end view state of a transition.

The Shader that is created using the shaderByteCode property as the underlying byte code. Each instance needs its own separate Shader, but can share the byte code. When each instance is played, create the Shader that the instance uses.

The bytecode for the pixel-shader program that the effect uses to animate between the two bitmaps. This property can be represented as either a ByteArray or as a Class representing a ByteArray (which is what results when you embed a resource).

The pixel-shader program can have arbitrary functionality and inputs, but must, at a minimum, have three image4 inputs. The first input, which can be named anything, should go unused by your pixel-shader program code - it exists only to satisfy the Flash requirement of assigning a filtered object to the first input. Note that inputs that go completely unused in a pixel-shader program might be optimized out, so your code should at least reference this input once.

There must be at least two other input bitmaps named from and to which represent the before and after bitmap images. Finally, you must define one float parameter named progress that contains the elapsed fraction of the effect.

You can specify two optional parameters, width and height. If they exist, they are automatically set to the width and height of the effect target.

See the Pixel Bender Toolkit documentation for more information on writing pixel-shader programs for Flash. You can also look at the source code for the CrossFade.pbk file in the frameworks\projects\flex4\src\spark\effects directory of the Flex source code.

The filter wrapped around the instance's shader property. This filter is assigned to the filters property of the target object with every update during the animation, so that animated updates to the underlying shader are reflected in the filter applied to the display object that the user sees.

A map of parameter name/value pairs passed to the pixel-shader program before playing. For example, to set a parameter named direction in a shader with a Pixel Bender pbj file in Wipe.pbj, the calling code could do the following:

       [Embed(source="Wipe.pbj", mimeType="application/octet-stream")]
       private var WipeCodeClass:Class;
       var shaderEffect = new AnimateTransitionShader();
       shaderEffect.shaderByteCode = WipeCodeClass;
       shaderEffect.shaderProperties = {direction : 1};
     

Constructor.