Comments on: Unfucking the ExternalInterface (1 of 2)

By: unterminated string

unterminated string — Sat, 03 Apr 2010 21:03:43 +0000

[...] mistake is assuming the behavior of the string replace method will impact all possible matches. …Calypso88 Blog Archive Unfucking the ExternalInterface (1 …… generated String as Argument, problems occurr if the string contains … const JS_CALL:String = [...]

By: Rob

Rob — Wed, 23 Dec 2009 19:33:49 +0000

Nice catch Ronnie, fixed it in the post.

By: Ronnie Swietek

Ronnie Swietek — Wed, 23 Dec 2009 19:00:08 +0000

I kept getting a foo is not defined error and changed the JS_CALL const to:

const JS_CALL:String = JS_FUNCTION + ‘(“‘ + ARG + ‘”)’;

and that fixed it

By: jeff karova

jeff karova — Mon, 28 Sep 2009 23:15:33 +0000

Has anyone had any issues with subsequent ExternalInterface calls? I’m using a time out method as mentioned here to make an ExternalInterface call, but it seems that any subsequent ExternalInterface call simply doesn’t occur. Oddly, it seems that every other ExternalInterface call is successful. Is there a way to ‘flush’ the ExternalInterface?

By: Rob

Rob — Sun, 13 Sep 2009 14:28:08 +0000

Good point quirx – although that’s more of a limitation of the ExternalInterface in general. Try calling escape() on your strings in JS, and unescape() when you receive the param in AS.

By: quirx

quirx — Sun, 13 Sep 2009 13:52:19 +0000

The Method works ok for functions with a predefined set of arguments. But if you somehow have a user-generated String as Argument, problems occurr if the string contains quotes or newline characters, etc.
Javascript will throw an error like “unterminated string literal…”
i wonder how we can fix this.

By: Jonathan Spooner

Jonathan Spooner — Thu, 08 Jan 2009 18:02:06 +0000

Good job! Saved me a bunch of time.

By: socketBridge: Flash - Javascript Socket Bridge » Matt Haynes - Programming & Tech Blog

Tue, 26 Aug 2008 16:30:11 +0000

[...] I found a way around this by wrapping all the callbacks from Flash in a setTimeout method. This effectively opens a new javascript thread and as such straight away returns the original callback. I picked up this tip here. [...]