What if you were able to pass in a view that is the containing view that you want to receive the dismiss tap, then add an action to it to call the expected dismiss method?
Hmmm, that won't work if there are other tappable items on the screen though. I just had this issue too last week, so I'll try to look up the solution when I get home, but I'll admit that my solution sucks. The bigger issue is that this is a common problem that must have been solved a boatload of times before we ran in to it, yet we don't have a consistent standard for implementing this. What we really want is a tap on any element that is not the UITextField to dismiss the keyboard, so simply setting the parent view controller to resignFirstResponder is not good enough, because other buttons can eat the tap that you would use for resignFirstResponder. Here are some questions. What happens if you wire up a dismiss call that issues a resignFirstResponder to the TouchUp Outside event? Do we need to rely on a full screen transparent button that sits one layer behind the UITextField that will issue a resignFirstResponser on the text field whenever we have a UITextField that we are editing? This must have been already solved in an elegant way that we're missing. What do you think? Cheers, Alex Zavatone On Apr 18, 2016, at 4:07 AM, Devarshi Kulshreshtha wrote: > Since I have to implement same behavior in multiple view controllers, I am > trying to identify a way to avoid using repetitive code in multiple classes. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
