Is this a hacky way to go to the next UITextField (using textFieldShouldReturn)?

Question

- (BOOL)textFieldShouldReturn:(UITextField *)sender
{
    if(sender.returnKeyType == UIReturnKeyNext){
        // Make something else first responder
    }else if(sender.returnKeyType == UIReturnKeyGo){
        // Do something
    }else{
        [sender resignFirstResponder];
    }
    return YES;
}

I have a UITextFieldDelegate using this. I'm new to iPhone dev stuff. Coming from web, I'm used to defining events dynamically and minimally. Is this an "ok" way to go from Username to Password UITextFields?

Is there a better common practice?

score 2 · Accepted Answer · edited May 23 '17 at 10:34

2

This has been discussed extensively here: How to navigate through textfields (Next / Done Buttons)

But the quick answer is yes, this is fine! Nothing hacky about it.

edited May 23 '17 at 10:34

Community

1
1

answered Sep 18 '11 at 19:47

jrturton

118,105
32
252
268

score 0 · Answer 2 · answered Sep 18 '11 at 19:45

0

If you have the text fields declared as properties of the class, you could simply compare sender to each text field to determine the correct course of action. I would probably do something like this.

- (BOOL)textFieldShouldReturn:(UITextField *)sender
{
    if (sender == self.firstTextField)
        [self.secondTextField becomeFirstResponder];
    else if (sender == self.secondTextField)
        [self doSomething];
    else
        [sender resignFirstResponder];

    return YES;
}

answered Sep 18 '11 at 19:45

Mark Adams

30,776
11
77
77

I like this. It's about the same as mine but gives me more control with my UITextFields. That's one thing I keep forgetting, not putting stuff in IBOutlets and such, instead just creating and adding them on the fly. – rnystrom Sep 18 '11 at 19:50

Is this a hacky way to go to the next UITextField (using textFieldShouldReturn)?

2 Answers2