Great, that's exactly what I wanted to know. For Flex 3, is there any way to free the children for garbage collection, hack or otherwise?
--- In [email protected], Gordon Smith <gosm...@...> wrote: > > In the Flex 3 states model, if you start in state A, go to state B which > creates and adds a child, and return to state A, the child is removed from > the display list but kept around. When you return to state B, it doesn't have > to be recreated and can just be re-added. > > In the Flex 4 states model, the default behavior is the same, but you can use > destructon policies to say that the child should not only be removed from the > display list but also freed for garbage collection. > > Gordon Smith > Adobe Flex SDK Team > > From: [email protected] [mailto:[email protected]] On > Behalf Of Geoffrey > Sent: Thursday, August 06, 2009 2:43 PM > To: [email protected] > Subject: [flexcoders] Instantiation of State Objects > > > > Are the objects for a state recreated every time a state is entered, or if > the object was created once, is it reused? > > Basically, I want to know if I swap between states, are the objects defined > by AddChild new instances every time I enter that state. >
