--- In [email protected], "stevekpeak8" <[EMAIL PROTECTED]> wrote: > > Thanks for the response, > > I'm not really trying to go between AVM2 and AVM3 for my actual > product. Yes, opening a Flex app in Flash AMOUNTS to doing so, but > that's just to try to get a better view of how to access the AVM3 > variables. > > All I'm trying to do is to gain access to some of the AVM3 variables > in my Flex swf so that my EXE wrapper can communicate with the SWF. > > BTW... Are there any utilities available that would let me peer > inside an AVM3 SWF? > > Thanks in Advance. > > Steve > > > --- In [email protected], leds usop <rptlead@> wrote: > > > > You cant access avm2(as2 swfs) scripts loaded within > > avm3 (as3 swfs -->flex swfs) and vice versa. Well at > > least not directly. If you forcibly load an as3 swf in > > flash 8, certainly you will not be able to see the > > scripts/ vars within except perhaps the version var. > > Same thing goes with loading as2 swfs within as3, > > unless you are using the as2 swf as assets for > > skinning and the like, you will lose the > > script-enabled functionalities in that as2 swf. You > > can check out the docs for more details about this. > > > > You may want to take a look at FlashInterface here: > > http://www.flashextensions.com/products/flashinterface.php > > > > although i think you will have to change which loads > > which... anyway, it's better than not being able > > to use your as2 functionalities entirely - unless you > > port all of them into as3 :) I hope that helps. Best > > of luck! > > > > -leds > > > > --- stevekpeak8 <stevek@> wrote: > > > > > Claus, > > > > > > Thanks very much for your reply. > > > > > > Unfortunately, I can't do this the way you suggest, > > > as I'm not > > > operating in a typical WEB environment. I'm in an > > > .EXE environment > > > using a tool called SWFKit. > > > > > > Here's the thing... If I take my output SWF, and > > > load it from within > > > Flash Professional 8, I can "list variables" from > > > the debug menu. > > > Using most SWFs that are created in Flash itself, I > > > CAN gain > > > visibility to many/all of the variables defined > > > within Flash. > > > However, from a SWF created in FLEX, I can only see > > > ONE variable: > > > > > > Level #0: > > > Variable _level0.$version = "WIN 8,0,22,0" > > > > > > And I AM able to see this variable from within the > > > SWFKit environment. > > > > > > There's GOT to be a way to mark other variables in > > > Flex to make them > > > appear in this exported list of variables, don't you > > > think? I'm > > > hoping that someone at Adobe can help me with an > > > MXMLC trick to > > > export variables to the Flash'variables' list. > > > > > > ANY HELP WILL BE GREATLY APPRECIATED. > > > > > > Thanks AGain, Claus > > > --- In [email protected], Claus Wahlers > > > <claus@> wrote: > > > > > > > > > > > > > When I define a VAR in Flex, I know that the > > > MXML compiler turns > > > that > > > > > into a FLASH variable in the output SWF But > > > What DOMAIN is that > > > > > variable listed in (for example _root in a > > > .FLA)? > > > > > > > > > > I need to know this because we're using SWFKit > > > to turn a SWF into > > > an > > > > > EXE, and I need the domain in order to get/set > > > Flex Variables > > > from > > > > > with in the SWF wrapper. > > > > > > > > You need to go the other way round: At startup of > > > your application, > > > grab > > > > the LoaderInfo.parameters object which contains > > > the variables > > > passed to > > > > your SWF from the outside, something like this: > > > > > > > > var flashVars:Object = root.loaderInfo.parameters; > > > > var myFlashVar:String = flashVars['myFlashVar']; > > > > > > > > Cheers, > > > > Claus. > > > > > > > > -- > > > > claus wahlers > > > > côdeazur brasil > > > > http://codeazur.com.br/ > > > > http://wahlers.com.br/claus/blog/ > > > > > > > > -- > > > > READ CAREFULLY. By reading this email you agree, > > > on behalf of your > > > > employer, to release me from all obligations and > > > waivers arising > > > from > > > > any and all NON-NEGOTIATED agreements, licenses, > > > terms-of-service, > > > > shrinkwrap, clickwrap, browsewrap, > > > confidentiality, non-disclosure, > > > > non-compete and acceptable use policies ("BOGUS > > > AGREEMENTS") that I > > > have > > > > entered into with your employer, its partners, > > > licensors, agents > > > and > > > > assigns, in perpetuity, without prejudice to my > > > ongoing rights and > > > > privileges. You further represent that you have > > > the authority to > > > release > > > > me from any BOGUS AGREEMENTS on behalf of your > > > employer. > > > > > > > > > > > > > > > > > > > > > > > > ______________________________________________________________________ > ______________ > > TV dinner still cooling? > > Check out "Tonight's Picks" on Yahoo! TV. > > http://tv.yahoo.com/ > > >
Hi Guys, Isn't this just an External Interface solution? Check out: -http://livedocs.adobe.com/flex/2/docs/wwhelp/wwhimpl/common/html/wwhelp.htm?context=LiveDocs_Parts&file=00001973.html -http://blog.everythingflex.com/2005/10/26/flex-2-externalinterface-api-sample/ -http://livedocs.adobe.com/flex/2/langref/flash/external/ExternalInterface.html With EI, you can open register methods within you Flex movie that can be triggered from you EXE wrapper. Hope this helps.
