|
Hi Michael, This makes sense to me. The creationComplete
event is fired on a container when all of its children have been created –
it doesn’t matter whether the children of each child have been
instantiated or not. As Jesse said, the childrenCreated event can be used to
tell when all of a container’s children have been created. Cheers, Ali -- Development Director iteration::two [EMAIL PROTECTED] Office: +44 (0)131 338 6108 This e-mail and any associated attachments
transmitted with it may contain confidential information and must not be
copied, or disclosed, or used by anyone other than the intended recipient(s).
If you are not the intended recipient(s) please destroy this e-mail, and any
copies of it, immediately. Please also note that while software
systems have been used to try to ensure that this e-mail has been swept for
viruses, iteration::two do not accept responsibility for any damage or loss
caused in respect of any viruses transmitted by the e-mail. Please ensure your
own checks are carried out before any attachments are opened. From: Hi all, a quick question
about view stack instantiation: If I have a view stack,
creation policy auto, with two children:
<mx:ViewStack creationPolicy=”auto”>
<components:ChildOne /> <components:ChildTwo />
</mx:ViewStack>
ChildOne.mxml:
<mx:HBox creationComplete=”trace(‘child one
created’)”>
<!-- stuff in here -->
</mx:HBox>
ChildTwo.mxml:
<mx:HBox creationComplete=”trace(‘child two
created’)”>
<!-- stuff in here -->
</mx:HBox> In what order are the creationComplete events fired for the
children? I seem to be witnessing behaviour where the creation complete events
are being fired immediately, when the view stack is instantiated, but the
actual components within the children are not being instantiated until the
selected index of the view is changed (as you would expect from
creationPolicy=”all”). Does this sound reasonable? Has anyone
experienced this kind of behaviour? I was under the impression that the
creationComplete event for the top-level components themselves would not fire
until the view stack index changed. (Apologies for the lack
of a complete code sample (spread across several files I’m afraid), but
hopefully what I’ve said is enough to explain the problem) Cheers, Mike.
-- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com YAHOO! GROUPS LINKS
------------------------------------------------------------------ This e-mail and any attached files are confidential and intended solely for the use of the individual to whom it is addressed. If you have received this email in error please send it back to the person that sent it to you. Any views or opinions presented are solely those of author and do not necessarily represent those the Emakina Company. Unauthorized publication, use, dissemination, forwarding, printing or copying of this email and its associated attachments is strictly prohibited. We also inform you that we have checked that this message does not contain any virus but we decline any responsability in case of any damage caused by an a non detected virus. |
- RE: [flexcoders] Creation events and view stack children Alistair McLeod
- RE: [flexcoders] Creation events and view stack child... Alistair McLeod
- RE: [flexcoders] Creation events and view stack child... Michael Herron
- Re: [flexcoders] Creation events and view stack child... JesterXL
