The browser is a big variable in latency of message-passing. You can confirm that many SWF will run at different rates in different browsers. The NPRuntime API is now implemented pretty well in today's popular browsers, but the size and timing of permissible messages may vary among implementations. http://www.mozilla.org/projects/plugins/npruntime.html
In this case, though, it looks like you're using the old "javascript:" pseudo-URL, and then polling immediately for a result. It may be better to wait a frame or two, or an interval, before checking whether the plugin-to-browser and browser-to-plugin communication cycles have finished. I don't know how many browsers would stop the plugin's execution during the attempted cross-app communication. jd/adobe _______________________________________________ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
