Thanks Carl, it works this way.
Maybe this should be handled in the tweenTo method.
But I still have several quesions :
- does it respect the original timeline speed ?
- does it fire events of nested timelines ?
- performance wise, creating a new tween each time is not the best. Isn't it better to use a TweenMax instead of TweenLitle, and dynamicaly change destinationTime ?