Databases
StackOverflow2013
Postsdbo
POWhy would One table view in a tab view work fine while the other starts under the nav bar?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy would One table view in a tab view work fine while the other starts under the nav bar?
    text
    copied!<p>I have an app I'm working on that uses a modified version of the master detail template. The app is document based so it stats with a table view that lists all the documents. Once a document is selected is slides in a tab bar that has three tabs, the first two of which are table views. Both table views have their own table view controller class that share a common custom superclass. The inheritance is <code>UITableViewController</code> -> <code>TMSTableViewController</code> -> <code>TMSExpensesTableViewController/TMSCategoriesTableViewController</code>. Whichever tab is first displays just as it should with the table starting below the navigation bar. The second tab to load however always starts at the top of the screen under the navigation bar so the first row and a half are hidden. If it was just one of the table views I would assume there was something wrong with the controller or view but I actually duplicated the scene for the first tab and even when they both had the same controller running them the second one still started at the top of the screen.</p> <p>Have I found a bug in iOS7 or is there some strange trick that I need to do when using multiple table views in a tab bar? </p> <p>The tables each display a single Core Data entity type and <code>TMSTableViewController</code> has all of the common code for dealing with the fetched results controller and most of the table view code as well. The only methods in the two subclasses are to configure the cell as appropriate based on which kind of entity is being displayed, set the fetched results controller to have to proper entity, and add the proper kind of entity when required.</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