Skip to content

Conversation

@Zakay
Copy link

@Zakay Zakay commented Sep 26, 2012

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant