RE: [flexcoders] Nested faceless components. keeping IDs and DataBinding

2005-12-28 Thread Matt Chotin
: Wednesday, December 28, 2005 1:37 AM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Nested faceless components. keeping IDs and DataBinding Hi Matt, Back posting huh! Thx for the answer. Now what I don't remember is if when we instantiate via the Array if the MXMLObject initialized

Re: [flexcoders] Nested faceless components. keeping IDs and DataBinding

2005-12-28 Thread Aldo Bucchi
@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Aldo Bucchi Sent: Wednesday, December 28, 2005 1:37 AM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Nested faceless components. keeping IDs and DataBinding Hi Matt, Back posting huh! Thx for the answer. Now what I don't remember

RE: [flexcoders] Nested faceless components. keeping IDs and DataBinding

2005-12-28 Thread Matt Chotin
@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Aldo Bucchi Sent: Wednesday, December 28, 2005 1:00 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Nested faceless components. keeping IDs and DataBinding Matt, Unless I have a bug in my compiler(s), I believe I cannot place inline

RE: [flexcoders] Nested faceless components. keeping IDs and DataBinding

2005-12-27 Thread Matt Chotin
I think we're going to allow nested ids in Flex 2. For Flex 1.5 though you might be able to make Person an MXMLObject which would then have its initialized() method called as it gets created. That call would pass the MXML document which created the object and you could then attach the person

Re: [flexcoders] Nested faceless components. keeping IDs and DataBinding

2005-12-27 Thread Aldo Bucchi
Hi Matt, Back posting huh! Thx for the answer. Now what I don't remember is if when we instantiate via the Array if the MXMLObject initialized will be called. You'd need to look at the Yes it is called. As with every faceless comp. Using the initalized() indeed allows me to set an id or