Hey all, I'm at the start of a new Flex 2 project and am evaluating whether heavy use of states is a good idea. I really like how states and the state management works in Flex 2. I've done some prototyping and have seen some really clean results by writing and binding to state managers. Anyway... I've been digging into the state management code (in the Flex 2 framework) a bit and have a concern...
From what I can tell DisplayObject children created with AddChild and removed with RemoveChild are only removed from the display list and not completely destroyed. I don't necessarily think this is bad. In general it's probably preferred. However, I'm concerned that with large applications with many screens and components and heavy use of states that this might cause memory / perf issues. It also isn't desirable if a state is only accessed once and never seen again. I'm considering overriding some of the default state management behavior in order to have a create / destroy scenario. Before I get too deep into it I wanted to get some thoughts. Does this sound like a valid concern? Do you think it will ever be an issue? Maybe I should just tackle it when / if it becomes an issue and not worry about it until then? Thoughts? thanks, Paul -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/flexcoders/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
