Quirks (or stuff not yet decided)

This section houses anything that may seem a bit odd such (fringe cases) that we just haven't yet decided what to do with (if anything).

DuplicatePropertyRuleTypes Discussion

Currently, any Tweens whether running or not are checked when the duplicate property rule kicks in. This may or may not be the best strategy. One alternative would be to only check against Tweens that are currently running. This can have some unintended side effects as well though. In the event a position Tween is running on someObject and it is paused for a second then a new position Tween is added the duplicate property rule would not kick in if it only checked running Tweens. That may or may not be the desired effect.

On the opposite spectrum, if the duplicate property rule doesn't ever check if a Tween is running (the current way it works) then it could remove Tweens that you have set to not be auto removed on completion that you may want to use again later. One way to work around that is to remove the Tween when it is complete (Go.removeTween) then re-add it when needed (Go.addTween). Another possibility is for GoKit to not destroy a Tween when it is removed and instead just remove it. That would allow you to simply re-add it at any time if you keep a reference to it around.