On 4/30/06, Manish Jethani [EMAIL PROTECTED] wrote:
If you set creationPolicy to none, you can create each child on your
own using the 'createComponentFromDescriptor' method.
Didn't realise you were talking about Flex 1.5. It's createComponent()
in that case.
Manish
--
Flexcoders
On 4/25/06, nahruka [EMAIL PROTECTED] wrote:
What I'm realising is that children are ALL created, in a sequential
fashion, but CREATED in fact. Why is this happening? Should I set a
creationPolicy property to none and then instantiate the views
manually? If so, which is the best way to do
I'm using the following ViewStack within my application:
mx:ViewStack id=myViewStack height=100%
cmp:FirstView id=firstView /
cmp:SecondView id=secondView /
cmp:ThirdView id=thirdView /
/mx:ViewStack
I've been reading about the ViewStack component and found that children
(except the first
>From Help:
Navigator containers such as Accordion, TabNavigator, and ViewStack
implement the auto policy by creating all their children immediately,
but wait to create the deeper descendants of a child until it becomes
the selected child of the navigator container.
So if you want to create
4 matches
Mail list logo
