OK, if you have more than one MXML file, then you have a document tree
where each mxml file represents a document whose parentDocument is the
parent of the top tag in that MXML file.  Thus some number of calls to
parentDocument should get you where you want to go.

 

________________________________

From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of neilwcameron
Sent: Friday, September 14, 2007 11:09 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: SWFLoader Issue

 

Thats just the thing, I'm accessing it from another component. :(

I'm trying a few things now to try and get the instantiated class and
call the functions from that...on it goes.

--- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com>
, "Alex Harui" <[EMAIL PROTECTED]> wrote:
>
> You shouldn't need Application.application unless you are accessing
from
> another component/document.
> 
> 
> 
> ________________________________
> 
> From: flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com>
[mailto:flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com>
] On
> Behalf Of neilwcameron
> Sent: Friday, September 14, 2007 8:02 AM
> To: flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> 
> Subject: [flexcoders] SWFLoader Issue
> 
> 
> 
> Hi Guys,
> 
> In my application I have a line of code that is used to set up my
> components:
> 
>
Application.application.mainDisplay.createComponentsFromDescriptors(true
> );
> 
> But when I try to load my app with SWFLoader for testing purposes, it
> fails because on the SWFLoader app, there is no such component as
> mainDisplay of course.
> 
> Is there anyways around this? I've tried quite a few things but to no
> avail. Any ideas?
> 
> Thanks
> 
> Neil
>

 

Reply via email to