As an afterthought, I guess it is by design.
If you trigger it, it probably uses the current state as a starting
point. I guess what is needed is a way to tell it to stop the current
animation if triggered again before it finishes, or ignore subsequent
requests until the current animation is complete.

I tried queueing effects, but had no luck.


You received this message because you are subscribed to the Google Groups 
"Prototype &" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to