Switching away from a ViewStack view does not destroy it. It stays around in memory so you can switch back quickly. Assuming you have enough memory, once you've visited all views, memory shouldn't grow quickly and switching should be fast. Creating stuff as you switch views is often the cause of slow switching.
On 2/25/14 12:05 PM, "Scott Matheson" <[email protected]> wrote: >Hi > My end users 5 of them, are telling me that on their "old" W7 PCs, a >mixture of devices they are all seeing 20sec to 120 sec to change from >one screen to the next, theses are simple viewstack changes > >each component in the view stack can be complex, working at the lower >level changing between view stack seems to be fine > >maybe this is a memory leak problem, I was thinking (maybe wrongly) that >as I move form view stack ID 3 to 0 all object created in index 3 >(dynamic item renders) would be cleaned by garbage collection, this may >not be correct as the components all access a singleton, which is never >deleted, would this stop the "old " component from being deleted so i am >ending up adding the component time and time again ? > > > ><mx:ViewStack id="masterNavigation" x="0" y="0" width="100%" >height="100%" change="masterNavigation_childIndexChangeHandler(event)" > > selectedIndex="{_uofsModel.activeMainMeunScreen}"> <!-- controling >the size of the pages with in the overall screen --> > ><ns:Login id="login"/> <!-- index 0--> > ><ns3:Pips id="pips" /> > ><ns1:Workmenu id="workmenu" /> > > > ><ns4:GoToPage id="GoToPage" /> <!-- 3--> > ><reports:StudentProgressReport id="studentReport" /> > ><!-- dynamic added seciotn at this ing 5 --> > > > ><s:NavigatorContent> > ><lesson:Lesson model="{_uofsModel.currentLessonModel}"/> > ></s:NavigatorContent> > ></mx:ViewStack> > > >________________________________ > >Disclaimer: This electronic mail and any attachments are confidential and >may be privileged. If you are not the intended recipient, please notify >the sender immediately by replying to this email, and destroy all copies >of this email and any attachments. Thank you.
