On Sunday 15 February 2009 11:09:28 timbob wrote: > The problem is that you are triggering a mousemove event _every_ time > you move the mouse within the <div>, and every single time you create > a Move effect. > So when you leave the <div> there is a mouseout event and also the > mousemove event from your last mouse movement. > > The flickering you see is the interference of the two created move > effects. Since script.aculo.us renders all ongoing effects "in > parallel", unless you specify otherwise. > > As a workaround you could use an extra Event.Queue for your menu, and > limit the effects in the queue to only one at a time. > This is a bit dirty, but it works sort of. Of course you can mess > things up if you move your mouse very fast (depending on the effects > duration) in and out of the <div>.
I do something similar in this file: http://svn.tuxfamily.org/viewvc.cgi/wikizzle_main/trunk/javascript/interface/modules/sidebar_hiding.js?view=markup In the animate method. Basically, I just cancel() the old events before starting new ones. I wasn't aware that you could limit queues or maybe I'd have tried that. IsolatedSingleton is just a specialised kind of wrapper for Prototype's Class that I wrote, see here for an explanation: http://jimhigson.blogspot.com/2009/01/prototype-singleton-classes.html -- Jim blog: http://jimhigson.blogspot.com/ web: http://wikizzle.org --~--~---------~--~----~------------~-------~--~----~ 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-scriptaculous@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 -~----------~----~----~----~------~----~------~--~---
