Thanks for your feedback.
I agree with your comment "unresponsive to user clicks". So what is the best practice approach so that the user is not restricted and the tweened elements are not left stranded on the "stage" obstructing the incoming tween, because a new animation was called. ...thinking.
Would it be something like:
----------------------
-many
-different
-tweens
-...
----------------------
buttons <1> <2> <3> <....
---------------------
button.clickEvent -> creates timeline and add that tween
If another button was clicked it is added to the timeline, in a queue. The user would still have to wait to see the effect of that last clickEvent.
Hmmm, maybe if a button was clicked during a tween, stop that tween immediately and somehow clear all elements, then start then last chosen tween.
I'd be interested in your thoughts.