definitely - parents call public methods on children, children fire events
to inform parents to call methods
i never call parent functions from a child
a
On 11 May 2010 18:15, jonathan howe jonathangh...@gmail.com wrote:
As soon as you removeChild on child1, it loses the reference to the
Did you mean to say removeChildAt(0)?
Have you tried Loader.unload()?
_ _ _
Erik Mattheis
Senior Web Developer
Minneapolis
T 952 346 6610
C 612 377 2272
Weber Shandwick
Advocacy starts here.
PRWeek Global Agency Report Card 2009 - Gold Medal Winner
The Holmes Report Global Agency of the Year
As soon as you removeChild on child1, it loses the reference to the parent.
If you want to continue on that tightly-coupled path, I would store a
temporary reference to the parent, then unload child one and use the
temporary reference to parent to load the new child.
The design I would choose is
3 matches
Mail list logo
