AS3 Loader and SWC v Source Files

playvue

After banging this around for the majority of the day, and with some help from a fellow dev (LunarRaid), we were able to determine that when loading a starling-swf into another starling-swf via an AS3 Loader object, the only combination of project references that would work is if one or both references the Starling source files as opposed to the Starling SWC file. If both references the SWC file, we would get a Type Conversion error to starling.display.DisplayObject on the resultant loaded object when attempting to add it to the loading swf's starling displaylist via addChild.

What is it about the SWC that made the class definitions and super classes unrecognizable when matched to another use of the SWC?

joshtynjala

You could try passing the -external-library-path argument to the compiler when building your child SWF. This will keep the compiled Starling classes out of your child SWF. If only the parent SWF includes the Starling classes, and then the child SWF will be forced to use the parent's version. This should avoid any conflicts.

playvue

Thanks, Josh. But we actually already tried that as well (saw it as a rec in this forum, actually), but I couldn't get that to work either. It's only when the child SWF uses the source that it execs properly.

playvue

As it turns out, using release builds completely resolves this issue. Both loader and load-ee SWFs can reference the SWC and include it in the code when building.