We are using Flex SDK 4.6.0.23201 (with built in AIR SDK 3.1.0.4880) for both
the Air application host and the SWF being loaded.
We gave up on the styling problem (loading the SWF in to the same
application domain).
We swapped it to load in to it's own application domain, ala:
*var appDomain:ApplicationDomain = new ApplicationDomain();*
var loader:URLLoader = URLLoader(event.target);
var context:LoaderContext = new LoaderContext(false, *appDomain*);
context.allowLoadBytesCodeExecution = true;
swfLoader.loaderContext = context;
swfLoader.addEventListener(Event.COMPLETE, loadComplete);
swfLoader.load(loader.data);
Doing this reintroduced the problem (we'd already been down this road) of
resizing. Once the app had loaded the SWF it was impossible to get it to
resize the content.
We solved this by subclassing SWFLoader and adding a new method (which has
access to the real content):
public function changeSize(height: Number, width: Number):void {
if (contentHolder is FlexLoader) {
const sm:DisplayObject =
FlexLoader(contentHolder).content as
DisplayObject;
if (sm) {
sm["setActualSize"](width, height);
sm["application"]["setActualSize"](width,
height);
}
}
}
We did stumble initially on this as we wanted to cast
FlexLoader(contentHolder).content directly to a SystemManager. However, even
though it looks like a SystemManager in the debugger the cast fails. Using
reflection to call setActualSize on the content (and its application) works
though.
We were baffled by this and could only assume it was something to do with
how the SWF file is configured/merged/built.
Any ideas on why that cast would fail?
--
Sent from: http://apache-flex-users.2333346.n4.nabble.com/
