A modern programming language that makes developers happier.

kotlinlang

Conflicting calls to `tween` cause an ugly flicker.  Is there a better way to avoid that than manually tracking Jobs?  Example in :thread-please:

```class TestScene : Scene() {
    override suspend fun Container.sceneInit() {
        val redBox = solidRect(100, 100, Colors.RED) {
            xy(0, 0)
        }
        launch {
            val firstJob = launch { redBox.tween(redBox::x[500], time = 3.seconds) }
            delay(1500)
            // firstJob.cancel() &lt;-- this fixes the issue but is cumbersome
            // at t=3000 when the first tween finishes, box jumps to 500, but then resumes its animation towards 0
            launch { redBox.tween(redBox::x[0], time = 3.seconds) }
        }
    }
}```

Ideally it would be great if tweens to a matching `V2` cancelled prior calls.  I don't know how feasible that is.

Sorry if I didn’t understand the question but why not change the time of first tween to 1.5 seconds? You can also simply remove inner launch statements and do something like
```launch {
    redBox.tween(redBox::x[500], time = 1.5.seconds)
    redBox.tween(redBox::x[0], time = 3.seconds)
}```


I think the animation API handles those situations (cancellating previous stuff by finalizing the animation or keeping the current properties). But have to check to be sure

Yeah this was a contrived example. This happens for example if I have a view that animates up or down when clicked, if you click it twice before the animation completes

I looked through tween's source code and didn't see anything checking for a pre-existing TweenComponent, but I'm no expert.

<https://github.com/korlibs/korge-next/blob/a80359dec7b8eb6fda93097ab6cb0c577271d135/korge/src/commonMain/kotlin/com/soywiz/korge/animate/Animator.kt>

That's not a tween but something different