1 Reply Latest reply on Aug 9, 2009 2:40 PM by Gregory Lafrance

    Should I use States or Create/Destroy objects


      I have an application with 6 tile windows, each is quite complex with datagrids, TileLists etc. One window runs a game with animations.


      Traditionally I would have created and destroyed each window as needed. However using states for this particular application would be a very clean and easy to manage solution (at least it will be in Flex 4) but I'm concerned about the overhead. I assume Flex only hides windows when they are not in the current state? If this is the case then is there a significant performance hit with having all 6 windows in memory at the same time (there is plenty of memory available)? ie. what's the perfomance hit with large but invisible datagrids, tilelists etc. or is drawing to screen the big permance killer so if they are invisible they are benign?