Is this component tag used as an itemRenderer? If so, I would reconsider your approach. It is rarely useful to attempt to manipulate a renderer from the "outside". Its behavior should be driven from its current dataProvider item and you should manipulate the rendere instance by updating the dataProvider.
What is your myMethod going to do? Tracy Spratt Lariat Services Flex development bandwidth available ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of dnk Sent: Thursday, January 22, 2009 12:09 PM To: [email protected] Subject: Re: [flexcoders] Re: opposite of outterDocument? On 22-Jan-09, at 9:00 AM, Amy wrote: > --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , dnk <d.k.emailli...@...> wrote: > > > > Is there something the opposite of outterDocument to access vars and > > methods inside of a mx:component tag? > > > > or is it as simple as (no where near my flex machine): > > > > <mx:Component id="something"> > > > > <custom:mycomp /> > > > > </mx:Component> > > > > > > <script> > > > > something.mymethod; > > If you're actually _in_ the component, then you can use this. > > Otherwise, check out > http://www.adobe.com/devnet/flex/articles/loose_coupling.html <http://www.adobe.com/devnet/flex/articles/loose_coupling.html> > http://www.adobe.com/devnet/flex/articles/graduating_pt1.html <http://www.adobe.com/devnet/flex/articles/graduating_pt1.html> > No the script is called in the mxml file that has the below code: <mx:Component id="something"> <custom:mycomp /> </mx:Component> This is why i had referenced the opposite of outerDocument - because it would accomplish the opposite of what I am trying to do (accessing methods, etc inside of a component tag). d .
