Ah, I forgot about outerDocument, as I'm one of those "loose-coupling nazi" types and don't use it :)
Of course, being a louse-coupling nazi has it's upside, in Smartypants-IOC :) -Josh 2009/1/19 Paul Andrews <[email protected]> > Josh is probably on the ball. Also check out outerDocument: > > The <mx:Component> tag defines a new scope within an MXML file, where the > local scope of the item renderer or item editor is defined by the MXML code > > block delimited by the <mx:Component> and </mx:Component> tags. To access > elements outside of the local scope of the item renderer or item editor, > you > prefix the element name with the outerDocument keyword. > > Paul > > ----- Original Message ----- > *From:* dnk <[email protected]> > *To:* [email protected] > *Sent:* Monday, January 19, 2009 12:16 AM > *Subject:* Re: [flexcoders] flex not seeing method - update > > Tried that, and same issue. > d > > > > On 18-Jan-09, at 10:54 AM, Paul Andrews wrote: > > Try making the handler public.. > > > > -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." Like the cut of my jib? Check out my Flex blog! :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [email protected] :: http://flex.joshmcdonald.info/ :: http://twitter.com/sophistifunk
