Revision: 7953
Author: chaase@adobe.com
Date: 2009-06-18 08:27:47 -0700 (Thu, 18 Jun 2009)
Log Message:
***********
Small PARB effects change (oversight, should have been in Monday's commit). This removes the Fade.affectVisibility property. We used to automatically side-effect the 'visible' property on target objects when they were faded out or in, and exposed the affectVisibility flag to allow the developer to deny this side-effect. PARB requested that we just have that behavior but not allow the developer to tweak it. Now, an object that is not visible will be set to visible if Fade fades it in (when manually played - transitions are a different situation). We do not, however, set the visible flag to false automatically when fading it out, because that seems just wrong.
QE Notes: Should have no impact - this flag was new, and we knew when it went in that we were probably removing it soon. No tests exist for it.
Doc Notes:
Bugs:
Reviewer: Hans
Tests: checkintests
Modified Paths:
**************
flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/Fade.as
flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/FadeI nstance.as
