For performance reasons, children are not created until the container is attached to the parent.
In general, this problem is a warning flag. It says that your central code is pushing information downward which means that it has knowledge of the visuals. Modern architectures prefer that visuals pull information from a central data model, and then you won't have this problem. I would discourage pre-filling a cache at startup time too. ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of vdeprojects Sent: Tuesday, March 25, 2008 9:47 AM To: [email protected] Subject: [flexcoders] Re: creating MXML components with new-operator in ActionScript --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "mavdzee" <[EMAIL PROTECTED]> wrote: > > Hi, > > I have noticed that when I create an MXML component in ActionScript, > that the children of the MXML component are not created until I add it > as a child of another component. Is there any way to force creation of > children before it is added? I tried playing with creationPolicy and > createComponentsFromDescriptors() but none of this helps. > > I want to fill a cache of MXML-components when the application > initializes. At this point the cached MXML components have no parent > yet, but I need to do some initialization on it's children too. > > Cheers, > Andrej > I'm having exactly the same problem. Any help would be greatly appreciated!!! thx in advance, Tom
