You can mix containers with different creationPolicy settings and change the order in which they are created and their children are displayed. Flex creates outer containers before inner containers, regardless of their creationIndex. This is because Flex does not create the children of a queued container until all containers at that level are created.

Setting a container's creationPolicy property does not override the policies of the containers within that container. For example, if you queue an outer container, but set the inner container's creationPolicy to none, Flex creates the inner container, but not any child controls of that inner container.

In the following example, the button1 control is never created because its container specifies a creationPolicy of none, even though the outer container sets the creationPolicy property to all:

<?xml version="1.0"?>
<!-- layoutperformance/TwoCreationPolicies.mxml -->
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml">
    <mx:HBox label="HBox1" creationPolicy="all" creationIndex="0">
        <mx:HBox label="HBox1" creationPolicy="none">
            <mx:Button id="button1" label="Click Me"/>
        </mx:HBox>
    </mx:HBox>
</mx:Application>
The executing SWF file for the previous example is shown below: