When claiming touch do it in an orderly fashion #118
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.
First let the handler claim it, then cancel it on the rest of the handlers.
I came across a bug when a hade a handler that worked as a proxy handler.
CCScrollLayer looped through the handlers and claimed/cancelled without any order, the bug was when it first sent cancel to the proxy handler which in turn checked for all the "subhandlers" it proxies events too that subhandler hasn't claimed the touch then cancel. And because the claim wasn't made first, the proxy handler cancelled the event on all subhandlers, which then ended up in a crash.