     private static var offsetRotation:Vector3D = new Vector3D();
     private static var offsetTranslation:Vector3D = new Vector3D();
     private static var offsetScale:Vector3D = new Vector3D();
+
+    /**
+     * These maps hold the properties and layout constraints used to
+     * set up automatic property animations based on state changes. They
+     * are populated when the effect instance is set up according to 
+     * the properties/constraints affected by each transform effect.
+     */
+    mx_internal var layoutConstraints:Object = new Object();
+    mx_internal var affectedProperties:Object = new Object();
+    
 
     //--------------------------------------------------------------------------
     //

                }
            }
        }
        // FIXME (chaase): autoProps automatically animates all transform properties
        // that are not explicitly specified via the effect properties.
        // This handles, for example, transitions, to pick up all changes and turn
        // them into motionPaths on the transform properties.
        // This is great, but may have unintended consequences, such as performing
        // an animated Rotate when only a Move was requested (but the rotation angle
        // change was picked up automatically).
        // Ideally, we would have this behavior for the superclass effect, but not
        // carry over into the Move/Rotate/etc. effects.
        for (s in autoProps)
        {
            var mp:MotionPath = new MotionPath(s);

                motionPaths = new Vector.<MotionPath>();
            motionPaths.push(mp);
        }
        if (propertyChanges && !disableLayout)
            // automatically animate layout constraints affected by this
            // effect instance if we are in a transition
            for (s in layoutConstraints)
                setupConstraintAnimation(s);
        super.play();
    }

