Greg Ligierko wrote:
If I did, then for sure there is a better method :)
I did not play with the onBeforeUnload JS event and don't know whether
overriding its handler could work with ExternalInterface. Perhaps you
already considered this. The JS dialog might be annoying but this
could be another alternative.
http://pro-thoughts.blogspot.com/2006/03/onbeforeunload-event.html
Hmm. Interesting, but I wouldn't rely on it. Thanks for the link though.
I think I'm about done with the whole thing now - I will implement the
timer.
Thanks for the heads-up.
Paul
g
Monday, January 18, 2010 (6:29:08 PM) Paul Andrews wrote:
Greg Ligierko wrote:
I do not have the feeling how user interacts with the buttons. I am
just guessing that each button will be clicked many times in one
sequence and after reaching the desired state (a,b,c,...c,d,a,B) user
will move the cursor to a next button (or close the window).
If this is the scenario, then maybe a mixture of - on roll out event -
and timer would be effective (still low traffic and save guarantee).
You've more or less described my original plan!
g
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
