Cepends on what your states are defined to do, but sounds like you're adding and removing children on the state change, which is pretty common. The view objects will still be in memory, just not on the display list and with no parent.
On Thu, May 8, 2008 at 10:31 AM, David Ham <[EMAIL PROTECTED]> wrote: > I have an app with two mx:States, component A appears in state A, and > component B in the same position in state B. When I'm in state A, > where is component B, and vice versa? > > I my tests they appear to both still be in memory and visible; does > Flex just shuffle their z-indexes? What does Flex do with them when > you switch states? > > Thanks, > > OK > DAH > >
