| Building and Deploying Flex 2 Applications > Building and Deploying Overview > Improving Startup Performance > Using deferred creation > About the creationPolicy property | |||
|
|||
|
|||
|
|||
To defer the creation of any component, container, or child of a container, you use the creationPolicy property. Every container has a creationPolicy property that determines how the container decides whether to create its descendants when the container is created. You can change the policy of a container using MXML or ActionScript.
The valid values for the creationPolicy property are auto, all, none, and queued. The meaning of these settings depends on whether the container is a navigator container (multiple-view container) or a single-view container. For information on the meaning of these values see Single-view containers and Multiple-view containers.
The creationPolicy property is not inheritable. This means that if you set the value of the creationPolicy property to none on an outer container, all containers within that container have the default value of the creationPolicy property, unless otherwise set. They do not inherit the value of none for their creationPolicy. Also, if you have two containers at the same level (of the same type) and you set the creationPolicy of one of them, the other container has the default value of the creationPolicy property unless you explicitly set it.
Flex 2.01
Send me an e-mail when comments are added to this page | Comment Report
Current page: http://livedocs.adobe.com/flex/201/html/layoutperformance_119_05.html