Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You have to use <code>prepareForSegue:sender:</code> to fire the equivalent of <code>didSelectRowAtIndexPath:</code>. (Empty out the latter.) Instead of pushing the new view controller on the navigation stack, the segue already has a property <code>destinationViewController</code> that will just work automatically. You can modify this property if you want to customize the new view controller. Make sure <code>segue.identifier</code> is correct!</p> <p>Also, from your question I notice some confusion about the controllers of view controllers. You mention two of these: the tab bar controller and a navigation controller. In storyboard, the setup should be like this: </p> <pre><code>TabBarController --(relationship)--&gt; NavigationController --(relationship)--&gt; ViewController --(segue)--&gt; next ViewController </code></pre> <p>Make sure all these are correct in storyboard and see if it works.</p>
    singulars
    1. This table or related slice is empty.
    1. POSegue firing but not pushing / UITabBarController / UITableViewController when cell clicked
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMundi
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSegue firing but not pushing / UITabBarController / UITableViewController when cell clicked
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COhey Mundi, thanks for your really fast answer. I tried following your advice, but wouldn't get any further. I removed the `didSelectRowAtIndexPath` - and dragged a segue from the UITableViewController to the next UITableViewController. I also added a little debug code to the `prepareForSegue`, but it isn't called, if I don't call it programmatically. So I tried and dragged the segue from the UITableViewController Cell to the final UITableViewController (the one that never shows up) and ran it again. Wouldn't work either. Stuck...
      singulars
      1. PO
      1. USJames Stone
    2. COthis is what the storyboard looks like (note the three connected screens, these are the ones that matter) http://imgur.com/fEGNF - "Controller Navigation" loads up each of the UITableViewControllers just fine - and I have code in the "Controller Program" to show 1 row. If I tap that, I'd like to perform another segue and show the "Controller Sessions". I have removed code now, only have this in the "Controller Program": `- (void)prepareForSegue:(UIStoryboardSegue *)segue sender:(id)sender { NSLog(@"controllerProgram:: prepareForSegue: %@", segue.identifier );` and it doesn't fire
      singulars
      1. PO
      1. USJames Stone
    3. COAccording to the picture **you did not do the setup as described** in my answer. The leftmost controller is the tab bar controller, the next one must be a navigation controller (which you are missing), and then the "program" controller.
      singulars
      1. PO
      1. USMundi
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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