If I lift my finger up off the first touch, then it will recognize the next touch just fine. It's only when I hold my first touch down continuously and then try and touch a different area with a different finger at the same time. It will then incorrectly register that second touch as being from the first touch again.
Update It has something to do with touchesEnded not being called until the very LAST touch has ended (it doesn't care if you already had 5 other touches end before you finally let go of the last one... it calls them all to end once the very last touch ends)
- (void)touchesBegan:(NSSet *)touches withEvent:(UIEvent *)event {
UITouch* touch = [touches anyObject];
NSString* filename = [listOfStuff objectAtIndex:[touch view].tag];
// do something with the filename now
}
- (void)touchesEnded:(NSSet *)touches withEvent:(UIEvent *)event {
ITouch* touch = [touches anyObject];
NSString* buttonPressed = [listOfStuff objectAtIndex:[touch view].tag];
// do something with this info now
}
I had this today, (or rather I had this problem dumped on me today!).
What I saw happening:
As Gavin Clifton said, it only happens if you add a gesture recognizer. Without a recognizer added, touchesEnded fires after each finger is released. Which would be great if I didn't need to use recognizers...!!!
I solved this by adding gestureRotation.delaysTouchesEnded = FALSE; to my recognizer creation/adding code:
gestureRotation = [[UIRotationGestureRecognizer alloc] initWithTarget:self action:@selector(gestureRotation_Callback:)];
[gestureRotation setDelegate:self];
gestureRotation.cancelsTouchesInView = FALSE;
gestureRotation.delaysTouchesEnded = FALSE; // <---- this line!!
[self.view addGestureRecognizer: gestureRotation];
[gestureRotation release];
Now the gestures work, and touchesBegan no longer queues!
For whatever reason, touchesEnded is being delayed only when the touch is within the scrollview. If you either a) disable the scrollview from scrolling; or b) don't use a scrollview, then touchesEnded gets delivered right away.
I have heard where some people have intercepted sendEvent, but that seems sketchy to me and I really don't want to screw up the responder chain since sendEvent handles an awful lot of events.
Any additional thoughts? Has anyone ever subclassed UIWindow to try and intercept the touches that way? Any input you could provide is appreciated.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With