In a web application I am working on there is a menu that slides down when you mouseover something and slides back up when you mouseout again. If you did this too quickly the result would be that the animation would bounce up and down quite comically with no way to stop it other than waiting for the jQuery animation queue to empty itself.
With jQuery 1.2 it seemed like a solution to this problem was available, because you can now stop animations. I tried adding stop() calls into the code in the belief that aborting the currently animation before startign a new one would solve my problems.
> interface_drag.js is basically a barebones version of the jQuery > interface library with just the bare nimimum needed for draggables > built into it.
If we can't see the code, it will be hard to judge where the error is. Have you got a page where we can see the error in action?
> > interface_drag.js is basically a barebones version of the jQuery > > interface library with just the bare nimimum needed for draggables > > built into it.
> If we can't see the code, it will be hard to judge where the error is. > Have you got a page where we can see the error in action?
> > > interface_drag.js is basically a barebones version of the jQuery > > > interface library with just the bare nimimum needed for draggables > > > built into it.
> > If we can't see the code, it will be hard to judge where the error is. > > Have you got a page where we can see the error in action?
I've found a few places in the interface plugin libs where the old version of dequeue is used; they need to be replaced with the new calls to work. The old version took two arguments, the new version uses jQuery chainability. For example:
On line 473 of ifx.js change : jQuery.dequeue(elem, "fx"); to: jQuery(elem).dequeue("fx");
On line 49 of ifxhighlight.js change: jQuery.dequeue(this, 'interfaceColorFX'); to: jQuery(this).dequeue('interfaceColorFX');
We're using jQuery and a large set of plugins for a web application, and these are the only two places I've encountered incompatibilities.
Christiaan
On Sep 12, 7:10 am, Gordon <gordon.mc...@ntlworld.com> wrote:
> In a web application I am working on there is a menu that slides down > when you mouseover something and slides back up when you mouseout > again. If you did this too quickly the result would be that the > animation would bounce up and down quite comically with no way to stop > it other than waiting for the jQuery animation queue to empty > itself.
> With jQuery 1.2 it seemed like a solution to this problem was > available, because you can now stop animations. I tried adding stop() > calls into the code in the belief that aborting the currently > animation before startign a new one would solve my problems.
> interface_drag.js is basically a barebones version of the jQuery > interface library with just the bare nimimum needed for draggables > built into it.
> I've found a few places in the interface plugin libs where the old
> version of dequeue is used; they need to be replaced with the new
> calls to work. The old version took two arguments, the new version
> uses jQuery chainability. For example:
> On line 473 of ifx.js change :
> jQuery.dequeue(elem, "fx");
> to:
> jQuery(elem).dequeue("fx");
> On line 49 of ifxhighlight.js change:
> jQuery.dequeue(this, 'interfaceColorFX');
> to:
> jQuery(this).dequeue('interfaceColorFX');
> We're using jQuery and a large set of plugins for a web application,
> and these are the only two places I've encountered incompatibilities.
> Christiaan
> On Sep 12, 7:10 am, Gordon <gordon.mc...@ntlworld.com> wrote:
> > In a web application I am working on there is a menu that slides down
> > when you mouseover something and slides back up when you mouseout
> > again. If you did this too quickly the result would be that the
> > animation would bounce up and down quite comically with no way to stop
> > it other than waiting for the jQuery animation queue to empty
> > itself.
> > With jQuery 1.2 it seemed like a solution to this problem was
> > available, because you can now stop animations. I tried adding stop()
> > calls into the code in the belief that aborting the currently
> > animation before startign a new one would solve my problems.
> > interface_drag.js is basically a barebones version of the jQuery
> > interface library with just the bare nimimum needed for draggables
> > built into it.
|
