I know ExternalInterface.call() is suppose to be used instead of fscommand, but I'm hitting an issue with getting it to work in my engine.

If I call the following I have the Flash player shutdown properly:


But if I try the "proper" way I get a weird hang in the player:


Has anyone else been able to get the player to quit cleanly with ExternalInterface?

I don't think you can simulate fscommand using ExternalInterface.

In AS1/2 getURL can be used as an alternative:
getURL("FSCommand:action", "param");

so I suppose it should also work that way using navigateToURL.

@Philippe I thought ExternalInterface.call() 's purpose was to supersede fscommand. At least with my day job, it's handled AS2 fine; I figured with AS3 it would be the same and it's just a bug in the player that "quit" is not
recognized.

http://www.adobe.com/livedocs/flash/9.0 ... html#call()

I also thought that maybe it was a limitation (that fscommand didn't have to adhere to) due to "Network Services" turned on but turning this off still resulted in the player locking up.

Well you can use fscommand to call a user-defined javascript function to handle custom commands. It's clumsy but it kind of works

However 'quit', 'fullscreen', etc. are handled specially by the host and AFAIK you can not send this commands using ExternalInterface.

That said ExternalInterface is really powerful, I encourage you to dig into it

Hi,

as you are talking about the use of ExternalInterface:
With ExternalInterface you can execute any javascript code you want (in browser of cource ). It's also superior to the well known navigateToURL because i.e. is buggy in in Internet Explorer but works nicely in all browsers

Lg
warappa

Actually it should be:

You had parents after 'history.back' which isn't correct - although it may somewhat work.

Technically, first parameter of .call() will be eval'ed in Javascript - a function is expected. This function will be called with any number of additional parameters that you can pass in ...rest to .call().

You can basically provide anything to be eval'ed, which allows you to do some nifty JS injection (bonus CDATA trick here for defining a multiline string):