Bizarrely enough, I get the same results regardless of which I choose... Gk.
--- In [email protected], "JesterXL" <[EMAIL PROTECTED]> wrote: > > Did you publish the Flash 8 SWF with Network access or Local access? > > ----- Original Message ----- > From: "Gregor Kiddie" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Monday, February 20, 2006 10:32 AM > Subject: [flexcoders] Re: Sandboxing issues? > > > I've loaded the Flash 8 swf into a Loader Object in the Flex App and > it gets called as with any other loaded object: > > <mx:HBox width="0" height="0"> > <mx:Loader source="AppComs.swf" autoLoad="true" height="0" > width="0" id="appComs" /> > </mx:HBox> > <mx:Button id="appPrint" label="Print" > click="scriptPrint.label=appComs.content.doPrint();" tabIndex="23" /> > > The return from the call is just ExternalInterface.available (don't > ask why it was done like that... please!) > > I'm getting a return of true from the Flash swf, but no communication > with the .NET control... surely if the swf was blocked from > communicating with the control, ExternalInterface.available would come > back false? > > Egor. > > --- In [email protected], "JesterXL" <jesterxl@> wrote: > > > > Flash 8 movies can only talk to local content only, or net content > only, not > > both. Your Flash 8 SWF is talking to .NET; how is it talking to > your Flex > > app? > > > > ----- Original Message ----- > > From: "Gregor Kiddie" <rogerg1979@> > > To: <[email protected]> > > Sent: Monday, February 20, 2006 6:13 AM > > Subject: [flexcoders] Sandboxing issues? > > > > > > This is quite convoluted so bear with me.. > > > > We are developing a large scale product using Flex 1.5 and it has been > > decided that interaction with the users system was required. > > > > This lead to the creation of a .NET control (broadcast via the net) > > that hosts our application and gives us the interactions we require. > > > > Flex movies don't play nice with their containers, so we decided to > > use a Flash 8 movie contained within a Loader object to use its > > ExternalInterface API to comunicate with the .NET control. > > > > Now when the control is run in a test environment everything works > > happily, however when used in a webpage, the flash 8 movie comes back > > with ExternalInterface.available = true and no errors are thrown, > > however no communication takes place with the .NET control. > > > > My intial suspicion was to do with the allowScriptAccess property > > being unable to be set, but as all the pieces of the jigsaw are coming > > from the same domain, there isn't any cross-scripting occuring... > > > > Anyone have any suggestions for a frustrated developer? > > > > > > > > > > > > -- > > Flexcoders Mailing List > > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > Search Archives: > http://www.mail-archive.com/flexcoders%40yahoogroups.com > > Yahoo! Groups Links > > > > > > > > > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com > Yahoo! Groups Links > -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
