Re: Stopping Multiple Clicks Thanks, Sarah.
FlushEvents doesn't stop the multiple clicks either. I think that this may be a bug. Apparently, the FlushEffects function does not work if clicks occur during animation (while objects are being moved). Because pending clicks aren't discarded when users click about the card during an animation, clicks to other buttons can trigger a *unique* chain of events: An animation will stop temporarily, wait while another clicked button executes its handler, and then start again. If the user clicks other *animation* buttons, multiple *move object* handlers will run on top of each other at the same time. Not only are pending mouseClicks allowed to be executed, but their scripts begin running immediately--intervening with or running simultaneously with the current *move object* handler. Ted ----- >I haven't used it myself, but I think the "flushEvents" command will do what >you need. >Sarah ----- >Stopping Multiple Clicks >I've been unable to clear the click buffer (to stop inadvertent repeated >clicks to objects) while an *animation* handler is running. Usually I use >*wait while the mouseClick* to stop multiple clicks; however, in Revolution I >have found that this does not discard clicks that occur during animated >sequences; that is, while objects are being moved via script (a likely time >for a user to start clicking). >For example, here's a recipe: >1. Create a graphic box about the size of your thumbnail, and name it "test". >2. Create a button, and add this script: >on mouseUp show graphic "test" at 68,180 move graphic "test" to 210,180 in four seconds wait while the mouseClick --discard additional clicks to objects >end mouseUp >3. Click the button, and *while the graphic box is in motion*, click the >button again. Rather than being discarded, the click jumps the script to the >beginning. >I have cards that contain multiple controls for triggering different short >animations. In Revolution, when a user begins clicking about on the card while >an animation is in progress, *wait while the mouseClick* has no effect; the >pending mouseClicks to other objects trigger yet more animations, producing >highly unexpected results. >Ted _______________________________________________ improve-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/improve-revolution
