The same general code should work for TabNavigator:

<?xml version="1.0" encoding="utf-8"?>
<mx:Application name="TabNavigator_addChild_test"
        xmlns:mx="http://www.adobe.com/2006/mxml"
        layout="vertical"
        verticalAlign="middle"
        backgroundColor="white">

    <mx:Script>
        <![CDATA[
            import mx.containers.HBox;

            private function addChildButton_click(evt:MouseEvent):void {
                var box:HBox = new HBox();
                box.label = "Child " + tabNavigator.numChildren;
                box.percentWidth = 100;
                box.percentHeight = 100;
                box.setStyle("backgroundColor", int(Math.random() * 0xFFFFFF));
                tabNavigator.addChild(box);
            }

            private function removeChildButton_click(evt:MouseEvent):void {
                if (tabNavigator.selectedChild != null) {
                    tabNavigator.removeChild(tabNavigator.selectedChild);
                }
            }

            private function removeAllChildrenButton_click(evt:MouseEvent):void {
                tabNavigator.removeAllChildren();
            }
        ]]>
    </mx:Script>

    <mx:ApplicationControlBar dock="true">
        <mx:Button id="addChildButton"
                label="Add child"
                click="addChildButton_click(event);" />
        <mx:Button id="removeChildButton"
                label="Remove child"
                click="removeChildButton_click(event);" />
        <mx:Button id="removeAllChildrenButton"
                label="Remove all children"
                click="removeAllChildrenButton_click(event);" />
    </mx:ApplicationControlBar>

    <mx:TabNavigator id="tabNavigator"
            width="100%"
            height="100%" />

</mx:Application>

Peter

Will the same code work to dynamically add a tab to a tabnavigator container?

Kirk

Apart from setting the creationPolicy property, I don’t have any other immediate ideas. And you tried setting the creationPolicy to “all”, or setting it to “auto” then “all”?

If you think it is a bug, file it at http://bugs.adobe.com/flex/ and solicit a few votes and then somebody at Adobe can take a look.

Peter

what about the contents of the remaining children? i’ve got an accordion setup in mxml that i reconfigure by deleting children. what i’m seeing is the contents of the remaining children (all List) aren’t getting rendered until the user changes the selectedIndex. i’ve tried pretty much all the tricks i know to get the List contents to render after deleting the child (creationPolicy, etc.) but no luck.

any ideas?

ps: i guess no need to keep repeating how much we love this blog, but what the heck, “we love this blog” ;-)

Awesome examples they are a huge help to new Flex-ers

The component is destroyed just like any other class–when it is not accessible from the application (when all references are destroyed). Having a parent is a reference so being on the display list by definition keeps something alive. Having a reference to the component such as an instance variable also could keep it alive.

In the above example, however, the component is created as a function-local variable and added to the accordion. No other reference is kept so in this situation, the component is eligible for garbage collection when it’s removed from the display list.

HTH,

Sam

“The RemoveChild class removes a child display object, such as a component, from a container as part of a view state. The child is only removed from the display list, it is not deleted.”

this will surely lead to memory leaking problems, and also forces me to reset the control’s contents each time they’re shown, how can I destroy a component?