Thanks for the reply Alex. One additional question, what would prevent updateDisplayList from being called after a component is added to the display list?
Further tracing shows that in the correctly drawn instance the updateDisplayList of the child components is called. In the one where the child subcomponents are not drawn it is not called. If I iterate over the children of the parent component it does list the subcomponents are being present. Thanks, - Ivo ----- Original Message ---- From: Alex Harui <[EMAIL PROTECTED]> To: [email protected] Sent: Thursday, May 29, 2008 2:56:00 PM Subject: RE: [flexcoders] what prevents a FlexEvent.CREATION_COMPLETE? If the child never finished validation because a call to updateDisplayList invalidates size or properties, you won’t get creation_complete ________________________________ From:[EMAIL PROTECTED] ups.com [mailto: [EMAIL PROTECTED] ups.com ] On Behalf Of ivo Sent: Thursday, May 29, 2008 11:42 AM To: FlexCoders Subject: [flexcoders] what prevents a FlexEvent.CREATION_ COMPLETE? Hello listers, I have a custom component I use in two locations in my app. In one instance it appears with all subcomponents laid out correctly but in the other it appears with an inner subcomponent blank, it is not drawn. This only happens on the web Flash Player tho, the same component under AIR shows both instances drawn correctly. Tracing I find that under AIR I can handle the FlexEvent.CREATION_ COMPLETE for the inner subcomponent for both instances. In the web version only one of them (the one that appears complete) triggers the event handler, the other one never gets triggered. I imagine this would cause the empty component symptom since this is dispatched once drawing is complete. The CREATION_COMPLETE event for the parent is always triggered tho. Thanks, - Ivo
