UIButton inside a view that has a UITapGestureRecognizer
Asked Answered
L

13

196

I have view with a UITapGestureRecognizer. So when I tap on the view another view appears above this view. This new view has three buttons. When I now press on one of these buttons I don't get the buttons action, I only get the tap gesture action. So I'm not able to use these buttons anymore. What can I do to get the events through to these buttons? The weird thing is that the buttons still get highlighted.

I can't just remove the UITapGestureRecognizer after I received it's tap. Because with it the new view can also be removed. Means I want a behavior like the fullscreen vide controls.

Leakage answered 27/7, 2010 at 13:54 Comment(0)
S
263

You can set your controller or view (whichever creates the gesture recognizer) as the delegate of the UITapGestureRecognizer. Then in the delegate you can implement -gestureRecognizer:shouldReceiveTouch:. In your implementation you can test if the touch belongs to your new subview, and if it does, instruct the gesture recognizer to ignore it. Something like the following:

- (BOOL)gestureRecognizer:(UIGestureRecognizer *)gestureRecognizer shouldReceiveTouch:(UITouch *)touch {
    // test if our control subview is on-screen
    if (self.controlSubview.superview != nil) {
        if ([touch.view isDescendantOfView:self.controlSubview]) {
            // we touched our control surface
            return NO; // ignore the touch
        }
    }
    return YES; // handle the touch
}
Spoke answered 27/7, 2010 at 22:29 Comment(5)
In my header file, i had my view implement UIGestoreRegognizerDelegate, and in my .m i added your code above. The tap never enters this method, it goes straight to my handler. Any ideas?Phototypy
@Phototypy you most likely forgot to set the UIGestureRecognizer delegate property.Angola
Can this answer be generalized to handle all cases where there is an IBAction involved?Allemande
@Martin IBAction compiles down to void so it doesn't leave any information behind at runtime to use for detection. But what you can do is walk up the view hierarchy, testing for UIControl, and returning NO if you find any controls.Spoke
thx for this, it helps me. if your button is in a UIImageView, make sure if userInteractionEnabled of the imageView is set at YES.Disconnected
L
159

As a follow up to Casey's follow up to Kevin Ballard's answer:

- (BOOL)gestureRecognizer:(UIGestureRecognizer *)gestureRecognizer shouldReceiveTouch:(UITouch *)touch {
        if ([touch.view isKindOfClass:[UIControl class]]) {
            // we touched a button, slider, or other UIControl
            return NO; // ignore the touch
        }
    return YES; // handle the touch
}

This basically makes all user input types of controls like buttons, sliders, etc. work

Linotype answered 5/9, 2011 at 4:14 Comment(2)
That's a flexible solution that can be accompanied with setCancelsTouchesInView = NO to not trigger tap gesture on interaction with controls. However you can write it better: return ![touch.view isKindOfClass:[UIControl class]];Crept
Swift 4+ solution: return !(touch.view is UIControl)Adriaadriaens
N
108

Found this answer here: link

You can also use

tapRecognizer.cancelsTouchesInView = NO;

Which prevents the tap recognizer to be the only one to catch all the taps

UPDATE - Michael mentioned the link to the documentation describing this property: cancelsTouchesInView

Nomology answered 17/1, 2012 at 7:28 Comment(6)
This should be the accepted answer IMO. This lets every subview handle the tap on its own and prevents the view which has a tabrecognizer attached to it from 'highjacking' the tap. No need to implement a delegate if all you want to do is make a view clickable (to resign first responder / hide the keyboard on textfields etc).. awesome!Willem
This should definitely be the accepted answer. This answer led me to read the Apple documentation properly, which makes it clear that the gesture recogniser will prevent subviews from getting the recognised events unless you do this.Bregenz
This used to work but now it is not working for me..perhaps because I have a scrollView under the button? I had to implement the delegate like in the answers above.Ennoble
After experimenting a little, I noticed that this will only work if the view which contains the gesture recognizer is a sibling of the UIControl, and it won't if the view is the parent of the UIControl.Ennoble
This is the best. Who knew that tap recognizers by default eat touches on the view? Who'd have guessed.Noli
Not really work as intended... YES, it's prevent tap recognizer to eat the event on UIControl. But it's still run the recognizer action, which is run 2 action at the same time.Nosy
A
73

As a follow up to Kevin Ballard's answer, I had this same problem and ended up using this code:

- (BOOL)gestureRecognizer:(UIGestureRecognizer *)gestureRecognizer shouldReceiveTouch:(UITouch *)touch {
    if ([touch.view isKindOfClass:[UIButton class]]){
        return NO;
    }
    return YES;
}

It has the same effect but this will work on any UIButton at any view depth (my UIButton was several views deep and the UIGestureRecognizer's delegate didn't have a reference to it.)

Augury answered 13/7, 2011 at 22:21 Comment(5)
Don't wanna be a dick here, but it's really YES and NO. Please use Cocoa conventions. TRUE/FALSE/NULL is for the CoreFoundation-Layer.Breeches
from what i've read, YES and NO were actually created for readability. readability is subjective. it stems from the method and property naming conventions which not everyone is overly concerned about. if you want strict adherence to naming convention then yes use YES and NO for any NSWhatever. however, i will say that if you survey developers you WILL get mixed opinions on which one of these is more readable [button setHidden:YES]; -or- [button setHidden:TRUE];Turkish
i guess what i'm trying to say is that if the premise of the naming conventions are readability then I think it's hard to deny that it's subjective in some cases. if you're a purist then you won't understand that statement.Turkish
It may seem subjective but after a while of Cocoa programming you really get into the more semantically accurate flow of code... the "TRUE" just seems really wrong now after years of Objective-C, because it does not match "hidden" very well.Glowing
Since when can/do you pass a tap gesture to a UIButton as a Touch Up Inside UITouch Event (the latter being the event generated by tapping a UIButton)? It seems duplicative and incorrect to create a tap gesture recognizer for a button that has 15 touch events already associated with a tap gesture. I'd like to see code, not guesses.Depart
H
12

In iOS 6.0 and later, default control actions prevent overlapping gesture recognizer behavior. For example, the default action for a button is a single tap. If you have a single tap gesture recognizer attached to a button’s parent view, and the user taps the button, then the button’s action method receives the touch event instead of the gesture recognizer. This applies only to gesture recognition that overlaps the default action for a control, which includes:.....

From Apple's API doc

Hectocotylus answered 20/11, 2013 at 10:16 Comment(0)
I
8

These answers were incomplete. I had to read multiple posts as to how to use this boolean operation.

In your *.h file add this

@interface v1ViewController : UIViewController <UIGestureRecognizerDelegate>

In your *.m file add this

- (BOOL)gestureRecognizer:(UIGestureRecognizer *)gestureRecognizer shouldReceiveTouch:(UITouch *)touch {

    NSLog(@"went here ...");

    if ([touch.view isKindOfClass:[UIControl class]])
    {
        // we touched a button, slider, or other UIControl
        return NO; // ignore the touch
    }
    return YES; // handle the touch
}
- (void)viewDidLoad
{
    [super viewDidLoad];
    // Do any additional setup after loading the view, typically from a nib.



    //tap gestrure
    UITapGestureRecognizer *tapGestRecog = [[UITapGestureRecognizer alloc] initWithTarget:self action:@selector(screenTappedOnce)];
    [tapGestRecog setNumberOfTapsRequired:1];
    [self.view addGestureRecognizer:tapGestRecog];


// This line is very important. if You don't add it then your boolean operation will never get called
tapGestRecog.delegate = self;

}


-(IBAction) screenTappedOnce
{
    NSLog(@"screenTappedOnce ...");

}
Illboding answered 18/8, 2013 at 23:51 Comment(0)
S
7

Found another way to do it from here. It detects the touch whether inside each button or not.

(1) pointInside:withEvent: (2) locationInView:

- (BOOL)gestureRecognizer:(UIGestureRecognizer *)gestureRecognizer 
       shouldReceiveTouch:(UITouch *)touch {
    // Don't recognize taps in the buttons
    return (![self.button1 pointInside:[touch locationInView:self.button1] withEvent:nil] &&
            ![self.button2 pointInside:[touch locationInView:self.button2] withEvent:nil] &&
            ![self.button3 pointInside:[touch locationInView:self.button3] withEvent:nil]);
}
Soloma answered 8/8, 2011 at 12:53 Comment(1)
I tried all of the other solutions for this, but the -pointInside:withEvent: approach was the only one that worked for me.Geronimo
G
7

Swift 5

Button on superview with tapgesture

 func gestureRecognizer(_ gestureRecognizer: UIGestureRecognizer, shouldReceive touch: UITouch) -> Bool {
    if let _ = touch.view as? UIButton { return false }
    return true
}

In my case implementing hitTest worked for me. I had collection view with button

This method traverses the view hierarchy by calling the point(inside:with:) method of each subview to determine which subview should receive a touch event. If point(inside:with:) returns true, then the subview’s hierarchy is similarly traversed until the frontmost view containing the specified point is found.

override func hitTest(_ point: CGPoint, with event: UIEvent?) -> UIView? {
    guard isUserInteractionEnabled else { return nil }

    guard !isHidden else { return nil }

    guard alpha >= 0.01 else { return nil }

    guard self.point(inside: point, with: event) else { return nil }

    for eachImageCell in collectionView.visibleCells {
        for eachImageButton in eachImageCell.subviews {
            if let crossButton = eachImageButton as? UIButton {
                if crossButton.point(inside: convert(point, to: crossButton), with: event) {
                    return crossButton
                }
            }
        }
    }
    return super.hitTest(point, with: event)
}
Germinal answered 5/12, 2019 at 23:7 Comment(0)
M
3

Here's the Swift version of Lily Ballard's answer that worked for me:

func gestureRecognizer(gestureRecognizer: UIGestureRecognizer, shouldReceiveTouch touch: UITouch) -> Bool {
    if (scrollView.superview != nil) {
        if ((touch.view?.isDescendantOfView(scrollView)) != nil) { return false }
    }
    return true
}
Mothy answered 2/6, 2016 at 15:18 Comment(0)
E
1

You can stop the UITapGestureRecognizer from cancelling other events (such as the tap on your button) by setting the following boolean:

    [tapRecognizer setCancelsTouchesInView:NO];
Eyelid answered 17/5, 2013 at 11:34 Comment(0)
C
1

If your scenario is like this:

You have a simple view and some UIButtons,UITextField controls added as subviews to that view. Now you want to dismiss the keyboard when you touch anywhere else on the view except on the controls(subviews you added)

Then Solution is:

Add the following method to your XYZViewController.m(which has your view)

- (void)touchesBegan:(NSSet *)touches withEvent:(UIEvent *)event
{
    [self.view endEditing:YES];
}
Chromate answered 23/5, 2013 at 6:22 Comment(2)
First I tried with @cdasher's answer but in my case even on clicking on button, Iam getting touch.view as my "view" in ViewController but not my "UIButton" control. Can someone say why the touch's view property is not returning the original view in which tap happenedChromate
Will not work if you have a scrollview or some other view that claims the touch events.Vyky
A
1

Optimizing cdasher's answer, you get

- (BOOL)gestureRecognizer:(UIGestureRecognizer *)gestureRecognizer
       shouldReceiveTouch:(UITouch *)touch 
{
    return ![touch.view isKindOfClass:[UIControl class]];
}
Augustineaugustinian answered 13/11, 2015 at 17:3 Comment(0)
V
0

Another option is to attach the UITapGestureRecognizer to some subView that is underneath the UIButton, instead of attaching to your main viewController view

Say you have a subView mySubView and teh buttons are stacked over it, but do not belong to it. Then you will create your tapGestureRecognizer as follows

var tapGetureRecognizer = UITapGestureRecognizer()
tapGestureRecognizer = UITapGestureRecognizer(target: self, action: #selector(theActionToBeTriggered))
    tapGestureRecognizer.numberOfTapsRequired = 1
    mySubView.addGestureRecognizer(tapGestureRecognizer)
Vulgar answered 14/2 at 16:2 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.