I didn't tried before on IE, and your answer opened my eyes ^^
I have already saw the article on James' blog, and i did like him and like your fla... and in fact, it works perfectly...only with IE ^^ but not with firefox...
Here's an example of two way communication between Flash Storyline. From Flash to Storyline it's pretty simple. From Storyline to Flash it employs a polling mechanism to check the state of a variable.
It sounds like your Firefox issue could be the Flash security sandbox at work. Is it failing for you locally or when hosted and run through http?
9 Replies
Hi Steven,
If you haven't already done so, take a look at this article on James' blog.
We created a timer SWF that communicates with Storyline using Jame's technique. You can read about it and download the sample from this thread.
Hope that helps...
Thanks a lot Steve !
I didn't tried before on IE, and your answer opened my eyes ^^
I have already saw the article on James' blog, and i did like him and like your fla... and in fact, it works perfectly...only with IE ^^ but not with firefox...
thanks again.
Steven, both of the examples I linked to in that thread seem to be working fine for me in Firefox. I just double-checked using Firefox 12.
- Steve
Well, i cheked too, i'm using Firefox 14.0.1.
And your example does not work on my version. I confess I am very disappointed. ^.^
Hmmm...I just updated to 14.0.1 and they still work for me. Maybe a security setting in Firefox needs to be set on your end?
Yes i think so ^^
Thanks again for your answer.
You do have "Enable Javascript" checked on Firefox's Tools > Options > Content tab, right?
Here's an example of two way communication between Flash Storyline. From Flash to Storyline it's pretty simple. From Storyline to Flash it employs a polling mechanism to check the state of a variable.
It sounds like your Firefox issue could be the Flash security sandbox at work. Is it failing for you locally or when hosted and run through http?
Steve & Steve,
This is wonderful information. Thank you both so much!
This discussion is closed. You can start a new discussion or contact Articulate Support.