I got it... I created a custom Event that I dispatch after the component has been completed. Then use that event handler of the component you where trying to access to work with the data that didn't exist until the object was created.
Ryan --- In [email protected], "Ryan" <[EMAIL PROTECTED]> wrote: > > Tracey, in that case how would get around this problem? I'm working a > very large flex app with the same problem. I have 100's of feilds and > staying true to MVC architecture I have everything as modules.... but > I run into this same problem. > > I agree it is bad practive, but short of creating a variable to house > each value and binding the text fields to that value I don't see a > working around, plus I hate to do that b/c I all those variables are > unnecessary. > > I would love some help here, > > Ryan > > --- In [email protected], "Tracy Spratt" <tspratt@> wrote: > > > > But creationPolicy="all" is bad practice, and you will be very sorry > > some day if you use it habitually. > > > > Tracy > > > > > > > > ________________________________ > > > > From: [email protected] [mailto:[EMAIL PROTECTED] On > > Behalf Of timgerr > > Sent: Monday, May 19, 2008 12:53 PM > > To: [email protected] > > Subject: [flexcoders] Re: Write Data to Tab Navigater > > > > > > > > Thanks, That worked well. > > > > --- In [email protected] <mailto:flexcoders%40yahoogroups.com> > > , "Battershall, Jeff" > > <jeff.battershall@> wrote: > > > > > > myTabNav.creationPolicy = "all"; > > > > > >
