Databases
StackOverflow2013
Postsdbo
POSetting the inputAccessoryView of a UITextField to its superview
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSetting the inputAccessoryView of a UITextField to its superview
    text
    copied!<p>I have a UITableView with an Add cell... row and would like to have a keyboard pop up with a view above it like in the "Messages" application, where the user can type the name of the new cell.</p> <p>I realize that there are several other ways to get user data, and several ways to implement the functionality that I am trying to achieve.</p> <p>For example, the iPod application presents a popup when a new playlist should be created.</p> <p>Right now, I have a hidden text field that is set to be the first responder when the Add cell... row is pressed, and I assign the view containing the input field and confirmation button as the inputAccessoryView for this hidden field. Alternatively, I could add this view as a subview of the table and position it using keyboard notifications.</p> <p>I would just like to know if there is a cleaner way to accomplish what I am trying to do (such as setting the inputAccessoryView of the input textField to be displayed to be the textField's superview). I have tried several approaches, but I cannot seem to be able to dismiss the keyboard using resignFirstResponder when the view should close. I can get the inputAccessoryView to disappear, but the keyboard remains resolutely open, taking up necessary screen real estate. Also, when the nib's view is a UITableView with a UITableViewController as the File's Owner rather than a UIView with a UIViewController as the File's Owner, I get a very odd error: "setting the first responder view of the table but we don't know its type (cell/header/footer)"</p> <p>Thanks in advance, Julian Ceipek</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload