Author Topic: Nuance of object.animate(index, seq)  (Read 779 times)

Offline KittenKoder

  • int
  • **
  • Posts: 66
  • I Am No One Else
    • View Profile
    • Kitt Games Wiki
Nuance of object.animate(index, seq)
« on: November 03, 2012, 05:35:55 am »
I don't know if it was intended or not, I actually like it, but the index value of 1.0 is actually "just before" the first frame interpolated with the last frame and not actually the very last frame of the sub-sequence. The only reason I bring this up is that the documentation does not mention this nuance and it may be nice to have it included in there, honestly I think the nuance is important for smoother animations anyway.

I noticed it by trying to write a non-cycling animation sub sequence driver class, it looked like it would cycle even though it was ending on the last point. Took me a lot of annoying back checking and cross referencing to realize what was really going on.  Now the challenge of figuring out a way to accomplish a non-cycling animation efficiently, I love challenges though.
When life throws you lemons, make lemon juice, then drop life into a pile of razors and pour the lemon juice over it.

Offline EgonOlsen

  • Administrator
  • quad
  • *****
  • Posts: 11749
    • View Profile
    • http://www.jpct.net
Re: Nuance of object.animate(index, seq)
« Reply #1 on: November 03, 2012, 08:04:22 am »
It's by design. You can disable it by setting the animation to use clamping instead.

Offline KittenKoder

  • int
  • **
  • Posts: 66
  • I Am No One Else
    • View Profile
    • Kitt Games Wiki
Re: Nuance of object.animate(index, seq)
« Reply #2 on: November 03, 2012, 08:28:45 am »
It's by design. You can disable it by setting the animation to use clamping instead.

You know, I hadn't thought of that, that would help a bit, thanks.

I was just pointing out that the documentation was unclear on that point.
When life throws you lemons, make lemon juice, then drop life into a pile of razors and pour the lemon juice over it.