Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Please do not create 21 different view controllers just to show different items. Instead set a property on <code>GlossaryDetailViewController</code> that holds an instance of your data model item.</p> <p>Consider this...</p> <pre><code>- (void)tableView:(UITableView *)tableView didSelectRowAtIndexPath:(NSIndexPath *)indexPath { NSInteger row = [indexPath row]; if (self.glossaryDetailViewController == nil) { GlossaryDetailViewController *aGlossaryDetail = [[GlossaryDetailViewController alloc] initWithNibName:@"GlossaryDetailViewController" bundle:nil]; self.glossaryDetailViewController = aGlossaryDetail; [aGlossaryDetail release]; } glossaryDetailViewController.glossaryDetailItem = [glossaryArray objectAtIndex:row]; [self.navigationController pushViewController:self.glossaryDetailViewController animated:YES]; } </code></pre> <p>Using this approach makes <code>GlossaryDetailViewController</code> responsible for setting it's own data.</p> <p><strong>Edit</strong> You'll also notice that I removed references to the app delegate. You don't need it to get access to the navigation controller. Each view controller in a navigation controller stack has a reference to it. While I'm thoroughly tearing your code apart, I would also factor out the creation of the view controller by overriding the getter for <code>glossaryDetailViewController</code>, like this:</p> <pre><code>- (GlossaryDetailViewController *)glossaryDetailViewController { if (!glossaryDetailViewController) { glossaryDetailViewController = [[GlossaryDetailViewController alloc] init]; } return glossaryDetailViewController; } </code></pre> <p>If you go this route, you can remove the <code>if</code> statement and just call <code>self.glossaryDetailViewController</code>.</p>
    singulars
    1. This table or related slice is empty.
    1. POPush a new view when a cell is tapped in Table View
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMark Adams
    1. USMark Adams
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POPush a new view when a cell is tapped in Table View
      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. VTUpMod
    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. VTAcceptedByOriginator
    1. COhey thanks, do you have like an example of how to hold an instance of a data for each cell? Thanks
      singulars
      1. PO
      1. USPatrickGamboa
    2. COSure, you subclass NSObject to make an object that will hold all of your related data that will be shown on `glossaryDetailViewController`. Then you would create your `glossaryArray` to hold those objects instead of NSStrings as you have now. Additionally you will add `glossaryDetailItem` as a property of `glossaryDetailViewController` with the same type.
      singulars
      1. PO
      1. USMark Adams
    3. COwow thanks, now that I am using this code, I ran into one tiny problem, I'm getting `glossaryDetailViewController.glossaryDetailItem = [glossaryArray objectAtIndex:row];` error because it's saying: Error: request for member 'aGlossaryDetail' in something not a structure or union. Any ideas? Thanks
      singulars
      1. PO
      1. USPatrickGamboa
 

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