for anyone who has emailed me regarding seeing the code for the solution; i dont like posting code for project that have not been released, but i can give you the jist o the solution so you can apply it to your specific needs.
I got everything (information wise) i needed to figure out the queue from the same link that joe.t posted above. (http://wiki.github.com/ madrobby/scriptaculous/effect-queues) read everything on that page to understand how it works first, but the important parts i used were the Effect.ScopedQueue and the clearing function: var queue = Effect.Queues.get('myscope'); queue.each(function(effect) { effect.cancel(); }); I used separate scoped queues for each item to be morphed, and when a rollover happened, it would clear the entire specific queue for an item, then add the new morph event to the queue. When a rollout happened it would also clear the entire specific queue for the item, then add the new morph event to the queue to be completed. This makes sure that when a new morph event it triggered on an item, it eliminates ALL OTHER morph events on that item, so there are never more than one morph event in queue on a specific item. This eliminates flickering caused by too many morph events being triggered and running/ending at different times. And it stops any other events that may have gotten mis-placed in the general queue from too many triggers being set off consecutively. Hope this helps, ill post the code after i publish the site this will be used for. -- You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to prototype-scriptacul...@googlegroups.com. To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
