Fix to ArgumentOutOfRangeException in handleUpdateOfType #38
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
prime31
added a commit
that referenced
this pull request
Oct 1, 2013
Fix to ArgumentOutOfRangeException in handleUpdateOfType
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In Go.handleUpdateOfType, if you remove/destroy a tween B in the onComplete method of a tween A, you sometimes get a ArgumentOutOfRangeException on the line 'var t = _tweens[i];'.
And I suppose that sometimes you don't get the Exception but you skip a tween.update() in the loop.
The fix I submitted here is to not remove immediately the tween when you call destroy() on it. It will be removed in the main loop in the Go class.