Multiple .start()
and .to(prop:[])
#602
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issues
Purpose of this Pull Request
This PR fixes the Issue of tween acceleration on multiple .start().
If an object with an array is passed to
.to()
,_valuesEnd
will be irreversibly changed when.start()
is executed multiple times.As a result, each time you run
.start()
, animation will be faster.Details of the changes
_hasSetupProperty
flag to check if_setupProperties()
has been executed..to()
, startValue will be changed to the current value of the tween target object. Check_valuesStart
and keep it if it is already initialized.tween.js/src/Tween.ts
Lines 169 to 172 in ae24c58
I used this code as a reference for change point 3.
Related pull requests
I think it might be difficult to merge this PR as-is, because of conflicts with features such as
dynamic to
and_propertiesAreSetUp
. In that case, I hope the added test cases will contribute to everyone.