Gordon may be able to answer this better but I thought I saw him say that we were firing that event too early in beta 1 and were fixing things to only do it after the children were actually created.

 


From: [email protected] [mailto:[email protected]] On Behalf Of Johannes Nel
Sent: Saturday, March 04, 2006 9:42 AM
To: [email protected]
Subject: [flexcoders] flex 2 creation policy

 

hi all

i have
<mx:VBox xmlns:mx="http://www.macromedia.com/2005/mxml" xmlns="*">
    <mx:Canvas id="__container">
        <innit:SomeComp id="__build" width="100%"/>       
        <container:SomeComp2 id="__tool" width="100%"   creationPolicy="none"/>       
    </mx:Canvas>
</mx:VBox>

where __tool's creationPolicy is set to none
then in a function is do this
    __tool.createComponentsFromDescriptors(true); to create this child

and in __tool's creationCompleteEvent i access some of its children.
this throws an error (found null  where it is expecting a child component)

is this expected behaviour. i would have expected creationcomplete in __tool to only fire once all its child components have been created, no matter what the creationPolicy of __tool is.

thanks
j
 


--
j:pn
http://www.lennel.org



--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




Reply via email to