There are two kinds of calls to MXMLDataInterpreter per instance.
The first one is generateMXMLProperties which handles the attributes in an MXML
tag. IIRC, this is called in the constructors in order to guarantee that the
baseclass calls generateMXMLProperties on its attributes before the subc
>You are welcome to investigate finding an efficient way to allow your proposed
>pattern.
What comes to my mind is interpreting before the atts. I’m finding It
difficult to understand how beadOffset is used in
MXMLDataInterpeter.initializeStrandBasedObject(). But can we use it to jump to
th
When I wrote this part of the lifecycle, I couldn't find an efficient way to
allow your pattern. So folks will have to instead use:
We should add that to the doc somewhere. You are welcome to investigate
finding an efficient way to allow your proposed pattern.
HTH,
-Alex
O
I’ve encountered a problem with MXML initialization of components that have a
model defined in MXML beads. Suppose I have the following MXML:
And the follow as3:
class MyComp extends UIBase {
public function set attName(value:*):void
{
model.attName = value;
