the last step is not rendered when the animation is playing

[javisantana]

looks like when the animation reach the last step it just jump to the step 0 without rendering the last frame

[fdansv]

@javisantana literally just started looking at this, so dismiss if it's nothing to do with the issue, but on the _tick function of Animator...

if(this.step() >= this.options.steps) {
    this._time = 0;
}

Shouldn't it be > instead of >= so that it doesn't skip the last step?

[javisantana]

@fdansv probably that's the issue

[fdansv]

As far as I can see, the last step is actually rendered, even though it instantly disappears because we're assuming the general use case for Torque is loads of points where the fact that the last one is only shown for a few millis is irrelevant.

However, on a timeline where every point is important for the visualisation there either should be an optional timeout upon reaching the end to allow the user to actually see the last point, or the user should disable looping.

[javisantana]

there is something I don't get here, in the original report we had:

torque-frame-count = 51
torque-time-attribute = "week" (being week in range [1, 52])
so torque should report 52 - 1 + 1 steps => 51

then, in the timeline, torque renders from 0 to 51 (frame 51 is rendered for a few milliseconds and you mention), that makes 52 steps. Why?