Home/ Questions/Q 5985787
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T22:34:48+00:00

I have a UITableViewCell with UITextField. In the edit mode, when the keyboard comes

  • 0

I have a UITableViewCell with UITextField. In the edit mode, when the keyboard comes up, the row I am trying to edit gets overlapped by the keyboard. Ideally the row should scroll up so that I can edit the cell.

I have searched stackoverflow throughly and found several different solutions. Most of them has to do with calculations to move or scroll the view up. Now there is a sample code from apple called TaggedLocations. They have the exact same behavior. And there is no code doing any complex calculations to move the view up.

I also thoroughly checked the IB interface and could not find any fancy thing going on either. If you download and run the code, it beautifully pushes up the row to a perfect position for the edit.

Does anybody know what trick is there in the TaggedLocations project which does this so elegantly? Location of the project:
http://developer.apple.com/library/ios/#samplecode/TaggedLocations/Introduction/Intro.html%23//apple_ref/doc/uid/DTS40008914

For the complex calculations I was referring, look at the following thread for example:

How to make a UITextField move up when keyboard is present?

thanks

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I figured out the problem.
    Initially I had

    TabBarController
    – UIViewController
    — UINavigationController

    — UITableViewController

    – UIViewController
    – -UINavigationController
    — UITableViewController

    With this kind of a hierarchy the table cells do not roll up when keyboard is displayed. But if I change the hierarchy to the following the rolling up happens just fine without any additional code!

    TabBarController
    – UINavigationController
    — UITableViewController

    – UINavigationController
    — UITableViewController

    When I duplicated the Apple code, I somehow messed up the hierarchy. Now on switching to the new hierarchy, it works fine.
    No additional code or calculation necessary.

    • 0