Pausing a tween from a Group removes that tween from the Group's array. about tween.js HOT 5 OPEN

This seems unintuitive indeed, so will mark as a bug. Do you have a sample? Here's a starting point: https://codepen.io/trusktr/pen/OJRQjZw

from tween.js.

Not sure if this small code was required, but here is the demonstration that the tween from a Group's array gets removed after pausing a tween:

const DATA = { 'X': 0 };
const TWEEN_DATA = { 'X': 1000 };
const TWEEN_GROUP = new TWEEN.Group();

new TWEEN.Tween(DATA, TWEEN_GROUP).to(TWEEN_DATA).duration(1000).onUpdate(UpdateCallback).start();

function UpdateCallback() {
    console.log(DATA);
}

function Animate() {
    requestAnimationFrame(Animate);
    TWEEN_GROUP.update();
}

Animate();

setTimeout(function () {
    console.log('Array Length Before Pausing: ' + TWEEN_GROUP.getAll().length);
    TWEEN_GROUP.getAll()[0].pause();
    console.log('Array Length After Pausing: ' + TWEEN_GROUP.getAll().length);
}, 500);

from tween.js.

Yeah, totally I see that. I meant, do you have an example of a problem this is causing?

Even long ago before TWEEN was made into a Group, and before there was pause(), Tweens were added or removed on start/stop:

So we need to see an example of the problem.

from tween.js.

I found a code related to this issue.

All tween instances hold a reference to a group. On pause, tween removes itself from a group and re-adds itself on resume.

Tween.update() skips paused tween. Because of this, it is not necessary to remove and re-add tweens to a group.

The downside of this behavior is that it can be confusing when users use Group to manage and manipulate their tween.

The advantage of this behavior is that the update loop is faster if the mainGroup holds a large number of paused tween.

from tween.js.

Ah indeed, should be easy to implement!

from tween.js.