Question: Setting "duration: 0" doesn't work as expected

[nltesown]

It is often useful to jump directly to the final state of an animation and jQuery.animate does just that when you set duration to 0. With velocity, duration: 0 apparently causes the animation to run in the default 400ms duration. A 1ms duration behaves as expected but is not a satisfactory solution when you need an immediate jump to the final state. Thanks!
(PS: your plugin is amazing!)

[julianshapiro]

Thanks, @nltesown :)

Supporting a true duration: 0 actually involves a series of hacks to avoid the requestAnimationFrame tick. It would likely be too considerable of a code reorg for me to implement.

However, I can make duration: 0 revert to 1 instead of 400. But, why is 1ms not satisfactory? What is your precise use case, if I may ask? I'd like to get an idea of use cases where someone would want to do this. There are likely more expressive ways to accomplish the same task.

[nltesown]

Hi Julian,
In my idea of how it should behave (which is the way jQuery.animate behaves, I think), a duration of 0 means that no animation runs at all. For that reason, duration: 1 is not OK because you actually run an animation (and generally get some unwanted flicker). I don't realize at all what it would imply for your code, but I figured it could be possible to simply skip any animation and directly set the final values... As for my use case: I'm translating some overflowing content within a container, and in some situations I need to directly jump from one position to another. I suppose it sounds vague or too specific, and it's true that I can find a workaround anyway... but in fact I was quite surprised when I followed the straightforward idea to set duration: 0 and saw that it didn't work as expected.

[julianshapiro]

Have you thought about using forcefeeding to achieve the same jumping effect? If you forcefeed a start value, Velocity will immediately start at that point. No flickering.

http://velocityjs.org/#forcefeeding

If that doesn't solve your issue, I'll look further into implementing a feature like you're describing.

[nltesown]

Thanks, I had not noticed this advanced setting, I'll have a look.

[TanguyS]

Actually, my first move was exactly the same (setting duration: 0). Maybe it would be more intuitive?

[julianshapiro]

K. I'm going to change 0 to default to 1 instead of 400. This change will be pushed tonight. Thanks, guys.

[TanguyS]

Thanks a lot Julian!

[julianshapiro]

@TanguyS, @nltesown

A duration of 0 now defaults internally to 1ms instead of 400ms.

Update your copies of Velocity.

Thank you!