ers@yahoogroups.com
*Subject:* [flexcoders] Re: creating instances, addChild question
thanks for the input Gordon,
When i think of creating mxml components, i'm thinking
lazy/convenience programming.
i want all the component and its children to be created. I can give
the children some de
erited styles aren't known until the component is attached to
its ancestors by addChild().
- Gordon
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of bhaq1972
Sent: Monday, April 30, 2007 1:50 PM
To: flexcoders@yahoogroups.com
Subject:
thanks for the input Gordon,
When i think of creating mxml components, i'm thinking
lazy/convenience programming.
i want all the component and its children to be created. I can give
the children some default values which i can then change after
the 'new', if i wish
eg My PrintView.mxml
Thanks Mike
this is great advice and knowledge.
> What problems are you facing without being able to access box
children after
> the new call and before the addChild() call?
I'm modifying a printing example from the livedocs which uses a print
template component. I was making a more generi
Hi,
Basically, you have to change the way you think about instantiation.
Calling the new operator creates memory allocation, accessibility, enables
and adds some listeners. This is like preinitialization.
What you now have to think is, addChild() is now the constructor of any
UIComponent.
If y
Thanks Mike
If i want to create a new instance of an mxml component, how can i
ensure its children get created as well.
--- In flexcoders@yahoogroups.com, "Michael Schmalle"
<[EMAIL PROTECTED]> wrote:
>
> the flow,
>
> new VBox()
>
> "I was wrong about the constructor calling initialize()"
6 matches
Mail list logo
