Skip to main content

Resigning keyboard on touch



I've found some code that helps me resign the keyboard when a user touches the screen off of the UITextView element.





Here's how it looks:







-(void)touchesBegan:(NSSet *)touches withEvent:(UIEvent *)event{

UITouch *touch = [[event allTouches] anyObject];

if([self.speechBubble.speechText isFirstResponder] && [touch view] != self.speechBubble.speechText){

[self.speechBubble.speechText resignFirstResponder];

}

[super touchesBegan:touches withEvent:event];

}







This works perfectly so far, and will remove the keyboard if a user touches anywhere outside of the text view. However, it only works for the particular object that I'm running it for, so if I have two speechBubbles, it won't work.





How can I change this so that ANY speechBubble will have the same effect? (I could move this code from my ViewController to my SpeechBubble class, but I'd have a little issue with how to use [touch view] to get touches outside of the speechBubble's view. ) Thanks


Comments

  1. Something I just discovered recently that may be of use to you is:

    [self.view endEditing:YES];


    It will resign first responder from any element that currently has it without you having to manually keep track of it yourself.

    In reference to your example code, something like this might work, depending on how your speechBubbles work:

    -(void)touchesBegan:(NSSet *)touches withEvent:(UIEvent *)event{
    UITouch *touch = [[event allTouches] anyObject];
    // Note the '!':
    if(![[touch view] class] isKindOfClass [speechBubble class]]){
    // It's not a bubble they touched, dismiss the keyboard:
    [self.view endEditing:YES];
    }
    [super touchesBegan:touches withEvent:event];
    }

    ReplyDelete

Post a Comment

Popular posts from this blog

Slow Android emulator

I have a 2.67 GHz Celeron processor, 1.21 GB of RAM on a x86 Windows XP Professional machine. My understanding is that the Android emulator should start fairly quickly on such a machine, but for me it does not. I have followed all instructions in setting up the IDE, SDKs, JDKs and such and have had some success in staring the emulator quickly but is very particulary. How can I, if possible, fix this problem?