That's the brute force way. It causes all
controls in all panes of the ViewStack to get created at startup, and so will
cause your app to start up slower. A better way is to initialize the control would
be in the childrenCreationComplete event on the pane of the ViewStack where it
lives. That event is dispatched when the user navigates to that pane, after the
controls on it have undergone deferred instantiation. You could also try simply writing a
creationComplete handler for the control itself. - Gordon From: Make the ViewStac's creationPolicy="all". ----- Original Message ----- From: Noah
Hoffman Sent: Tuesday, September
27, 2005 8:20 PM Subject: [flexcoders] Force
initialization of ViewStack children? I’ve got a component that’s not the first
component my View Stack and I need it to initialize on launch. Does
anyone know how to force this? Thanks, Noah
|
- RE: [flexcoders] Force initialization of ViewStack children? Gordon Smith