For testing/development, you can override the Viewstack instantiation behavior by setting creationPolicy="all".
This causes all child containers to be immediately instantiated and available. You will be able to see if the SO stuff works. Now, depending on your situation, you might not want to give up the user experience improvements(provided by deferred instantiation) entirely. You can programmatically instantiate a child, I don't remember the method offhand. You could also an event in the child container, maybe creationComplete, to do your SO work. Tracy -----Original Message----- From: Tom Fitzpatrick [mailto:[EMAIL PROTECTED] Sent: Thursday, April 07, 2005 4:36 PM To: [email protected] Subject: RE: [flexcoders] Viewstacks and paths Tracy - thanks. Is there a way have the viewstack populate the datagrid after the user has navigated to it? Or some other way to get around or deal with the deferred instantiation? At 02:51 PM 4/7/2005, you wrote: >Remember that ViewStacks use deferred instantiation by default, and so >the child containers (and the dataGrid)do not exist until the user >navigates to them. Yahoo! Groups Links Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> 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/
