Home/ Questions/Q 318505
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T08:34:32+00:00

In many situations, such as making the keyboard go away when the use clicks

  • 0

In many situations, such as making the keyboard go away when the use clicks done, there are two options: set the text field’s delegate to self, and adopt the UITextFieldDelegate protocol, and then use the method 

- (BOOL)textFieldShouldReturn:(UITextField *)textField;

to resignFirstResponder and return YES. But you can also 

      addTarget:self 
         action:@selector(myMethod:) 
forControlEvent:UIControlEventDidEndOnExit];

or something like that, using the did end on exit event, and then in the method, [sender resignFirstResponder]. So what is the best option in situations like these: the delegate, or the event?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If you are going to be paired with one other class, where the real type of that class may vary, then it makes a lot of sense to formalize that pairing into a protocol and a delegate arrangement.

    If the information you want to send is targeted at a broader set of objects, then it starts to make more sense to use notifications – though now you have somewhat obscured what information is being passed by the notification as there’s no central definition for what to expect.

    Both are about an equal load to work with – with a delegate you have to set yourself and then remember to unset yourself before you are deallocated. You have to do the same thing with notifications, remember to start listening and then unsubscribe before you are deallocated.

    Also, you should try as much as possible to make sure you send notifications out on the main thread as the notices get sent on the same thread they started from. Same goes for delegate methods, it’s not very kind to call a delegate method from some other mystery thread!

    • 0