Saad
Content Type
Profiles
Forums
Store
Blog
Product
Showcase
FAQ
Downloads
Posts posted by Saad
-
-
The architecture is shell.swf -> a.swf -> b.swf
shell.swf loads a.swf which in turn load b.swf
For some reason shell.swf displays only a.swf
Interestingly when I run a.swf on it's own it does load and display b.swf
not sure what I'm missing here.
Note: I'm getting access to document class for each loaded swf, instantiating and then adding as a child to the parent. Context
http://greensock.com/forums/topic/10992-how-to-access-flashdisplayloader-used-by-the-swfloader/
-
Got it...
var className:String = getQualifiedClassName(loaderMax.getContent("capture").rawContent); var loader = loaderMax.getContent("capture").rawContent.loaderInfo.loader; var classRef:Class = loader.contentLoaderInfo.applicationDomain.getDefinition(className) as Class; trace(classRef);
-
I'm trying to get hold of flash.display.Loader used by the SWFLoader in order to manually instantiate/setup the custom document class used by the SWF.
typically in as3, we'd use flash.display.Loader as below.
var className:String = getQualifiedClassName(loader.content); var classRef:Class = loader.contentLoaderInfo.applicationDomain.getDefinition(className) as Class; var captureModule = new classRef(); addChild(captureModule as DisplayObject);
LoaderMax routine
loaderMax.append(new SWFLoader("capture.swf", {name:"capture"}));
completeHandler, stuck at trying to get the loader object, seems it's private. Any suggestions please?
function completeHandler(event:LoaderEvent): void { var className:String = getQualifiedClassName(loaderMax.getContent("capture").rawContent); var loader = loaderMax.getLoader("capture"); //It's SWFLoader //var classRef:Class = loader.contentLoaderInfo.applicationDomain.getDefinition(className) as Class; //trace(classRef); }
deep nesting via SWFLoader
in Loading (Flash)
Posted
Hi Carl
Same problem with (AS3 Loaders + Document Class Instantiation), this seems like a flash bug to me, deeply nested clips won't appear if they are instantiated using document classes, however they exist in memory and are responding to function calls.
Everything works and displays if I don't choose the route of Document Class instantiation and instead just add the loader.content, however, this will defeat the purpose if wanna instantiate/add a loaded swf multiple times.