That thread I think is about loading a child SWF that was not a Flex
Application.
Let's collect some information first:
-What version of Flex are you using for the browser version?
-Are you using the same version of Flex for the AIR version?
-What is the URL of the main SWF?
-What is the URL of the sub SWF?
-What does the SWFLoader MXML tag (or AS equivalent) look like in the browser
version?
If you can't post your code as-is, anything sensitive can probably be
obfuscated.
If you can create a simple test case that works in the browser but not in AIR
that might help as well.
I can't immediately think of any constraints in AIR that don't allow it to
duplicate loading subSWFs like Flash can, other than the default security
rules. IIRC, by default, in Flash, a SWF loaded from the same domain from some
child folder is in the same security context and gets a child ApplicationDomain
topology. In AIR, a SWF loaded from a server or folder outside of the
application folder are put in different security contexts (like cross-domain
loading). The loadBytes trick puts the SWF bytes in the same security context,
but does not default to a child ApplicationDomain topology. I think some
aspects of Flex styles count on a child ApplicationDomain topology.
You can dump out the ApplicationDomain topology I think by accessing the
systemManagers in SystemManagerGlobals.
HTH,
-Alex
On 9/9/19, 1:43 AM, "DarrenEvans" <darren.ev...@allocatesoftware.com> wrote:
I played around with various of these techniques and they all present
different problems. Loading the child SWF into its own Application Domain
sorts out the styling problem but presents a different problem. Upon resize
nothing happens; the child SWF remain the same size or scales rather than
resizing (depending on SWFLoader settings).
I found this old post you commented on:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fforums.adobe.com%2Fthread%2F430250&data=02%7C01%7Caharui%40adobe.com%7Cda33622635514146a84f08d73501bf12%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637036153961495380&sdata=uDcpoeliFB0XKlN3PW6AYlYKk4D3Ns8f0IMRQwAfuao%3D&reserved=0
<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fforums.adobe.com%2Fthread%2F430250&data=02%7C01%7Caharui%40adobe.com%7Cda33622635514146a84f08d73501bf12%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637036153961505373&sdata=B4%2BvAdyPWCuADTlylzsN%2FdZvjXXAfz0x9Ls8sOJzieA%3D&reserved=0>
I'm not sure what you mean when you say "It might be worth it to implement
IFlexDisplayObject.". The child SWF is an mx:Application which already
implements that interface via its class hierarchy. Do you mean the launching
application?
--
Sent from:
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-users.2333346.n4.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7Cda33622635514146a84f08d73501bf12%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637036153961505373&sdata=W2S4fL9bqvtVRQNrZpc2nwKeRpghEmrQJFqbrUE1aTs%3D&reserved=0
