Tween.stop(true) fires onComplete event without target

[NiMeDia]

Dear Phaser team,

facing an issue where I call the tween.stop function with a true complete flag.

All I wonder is why in this case the tween.target isn't forwarded to the onComplete event, like it is done in the update loop.

I am currently expecting the tweens target in my event handler, not the tween itself as the first argument, what results in an exception if I complete the tween manually.

Think it would be better if the interface is the same for all cases, correct me if I am wrong.

[pnstickne]

Is there an online demo (a jsbin/codepen, etc) of the problem available?

The question is not clear to me as described.

[NiMeDia]

It's about the tween stop function (https://github.com/photonstorm/phaser/blob/master/src/tween/Tween.js) line 345. There is onComplete event dispatched like "this.onComplete.dispatch(this);"

At the other side in line 780 the event is fired like "this.onComplete.dispatch(this.target, this);".

So if I register an event handler like

tween.onComplete.add(function(target, tween){
 //some stuff
});

the target will be the tween if i call "tween.stop(true)".

[photonstorm]

Yeah that's fair enough - have made them consistent.

[NiMeDia]

Thanks alot!