I was using flash to track Google Analytics with PrettyPhoto and jquery carousel.

i finally found the solution thanks to this article… now I can save face in front of the client tomorrow.

function SendDataToFlashMovie(id)
{
var flashMovie=getFlashMovieObject(”_colorizeid”);

flashMovie.updateColorJs(id);

}

function getFlashMovieObject(movieName)
{
if (navigator.appName == “Microsoft Internet Explorer”)
{
var div = document.getElementById(”primary_block”);
var flash = div.getElementsByTagName(movieName);
return window.document[movieName];
}
if (document.getElementById(movieName) )
{
return document.getElementById(movieName);
}
}

where :
- movieName is : attributes.id
- primary_block is a first level div, in which the swf’s div is placed

swfobject.embedSWF(”mySwf.swf”, “image-block”, “300″, “300″, “9.0.0″, “expressInstall.swf”, flashvars, params, attributes);

Add this at the end of your AC_FL_RunContent parameter list:

,’id’,'yourSWF’, ‘name’,'yourSWF’

Then add this to your object class parameters:

Of course, “yourSWF” is whatever you want to call the thing.

Now I’m calling javaScripts off the page (even with jQuery) in Firefox 3, IE7, Chrome, Safari (Win) and Safari (Mac).

Check this site out:
http://blog.warptube.com/2008/12/2/oddities-with-externalinterface-and-ie

A really ugly issue with ExternalInterface can come up with naming your functions. You’re code will throw an error in code that looks something like:

function __flash__addCallback(instance, name) {
instance[name] = function () {
return eval(instance.CallFunction(”” +
__flash__argumentsToXML(arguments,0) + “”));
}
}

If you use: play, stop, tags, item, length, and likely some others I’m unaware of you will get an error inside Adobe’s JavaScript hook code. What’s happening is you inadvertently are screwing with some read only attributes of some IE functionality which is causing things to grind to a halt. My solution is to just prepend all my addCallback routines with an underscore.

I ran into similar issues using dynamically-generated elements with Externalnterface + Flash 10 + IE 7 + SWFObject 1.5. The fix for me was to ensure that whatever element I ended up calling SWFObject.write() on was previously appended to the DOM using appendChild() or somesuch.