Yeah it is backwards for me. I would have to change every swf loaded for this to work. The byteArray suggestion is the best suggestion so far, gotta try that out :-)
I've actually solved my problem in an unorthodox way currently. I've written a check method that does a describeType on the content of the Loader and if it sees that it implements the proper interface and also has all the proper methods it oks the swf. To actually call the methods of the loaded swf I had to use an untyped var - then it doesn't complain. I only do this after my check method has ok'd it. Thanks, John 2008/4/24 Ian Thomas <[EMAIL PROTECTED]>: > Hi Peter, > > It's the first time I've come across sandbox bridging. It's a nifty idea. > > The Flash documentation for it is here: > > http://livedocs.adobe.com/flex/3/langref/flash/display/LoaderInfo.html#childSandboxBridge > > But... unfortunately I think it's backwards for John's problem. It > allows a parent SWF to expose properties to a child SWF, rather than > the other way around... > > Ian > > On Thu, Apr 24, 2008 at 9:58 AM, Peter B <[EMAIL PROTECTED]> wrote: > > Could sandbox bridging help here? > > > > http://www.adobe.com/devnet/air/ajax/quickstart/sandbox_bridge.html > > > > This example descibes loading local HTML files, but the same rules > apply... > > > > Pete > > > > > > _______________________________________________ > > Flashcoders mailing list > > Flashcoders@chattyfig.figleaf.com > > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > > _______________________________________________ > Flashcoders mailing list > Flashcoders@chattyfig.figleaf.com > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
