> Event.REMOVED

Containers cannot use this since their child list is not updated.

UIComponent listens to the Event.REMOVED and stops propagation of it so
there is no way to listen for it. The component will then dispatch
FlexEvent.REMOVE at the correct time after child lists are correctly
situated.

This is what I was trying to say in my original comment to the OP. I used
CHILD_REMOVE, CHILD_ADD but FlexEvent.REMOVE and FlexEvent.ADD is the same
really except backwards.

Mike

@Tom

> Helping to biannually compete 24/7 magnetic convergence

Wow, this is freaky, I love reading your constantly changing signatures. :)


On Wed, Sep 24, 2008 at 6:00 AM, Samuel Colak <[EMAIL PROTECTED]>wrote:

>
> All objects dispatch FlexEvent.Remove when they are removed from a
> container - this occurs on the stage and also
> in Container objects (since Container and Stage both exhibit the same
> behaviour).
>



-- 
Teoti Graphix, LLC
http://www.teotigraphix.com

Teoti Graphix Blog
http://www.blog.teotigraphix.com

You can find more by solving the problem then by 'asking the question'.

Reply via email to