This content has been marked as final. Show 4 replies
Need more details on your problem scenario, simplified sample code.
The default behavior of a viewstack is to only create the screen your are currently viewing. So changing stacks will then force the viewstack to build everything laid onto the new stack at that moment. This type of behavior is set through a property called creationPolicy. The live docs page about it is here. Setting the creationPolicy to all will force the viewstack to build all of the children so that you may access them from anywhere without having to wait but be careful, if you tell it to build to much you'll see drastic performance issues.
I found 2 way for sol this problem
1.Use creationPolicy="all" easy to use, large resource used
2.Use callLater(method:Function, args:Array):void access when component available
Best solution is to use binding or your own event structure to populate the child data structures on creation and/or show, etc.