Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In iOS 4 and before, you are not supposed to create your own UIViewController hierarchy, so you have to manipulate views <em>directly</em> as subviews of a UIViewController's view.</p> <p>However, if you do this correctly, there <em>is</em> still a UIViewController hierarchy and it does still work. There is no circumstance in which you "do not have a reference" to the UINavigationController. A view has a superview, which is another view. A UIViewController's view has a reference to the UIViewController (as its <code>nextResponder</code>). The UIViewController has a reference to its parent UINavigationController if there is one.</p> <p>If that's not the case, you're doing something very wrong with view controllers.</p> <p>Apple's documentation says this (for iOS 4 and before), and you should take it very seriously:</p> <blockquote> <p>You should not use multiple custom view controllers to manage different portions of the same view hierarchy. ... If you want to divide a view hierarchy into multiple subareas and manage each one separately, use generic controller objects (custom objects descending from NSObject) instead of view controller objects to manage each subarea. Then use a single view controller object to manage the generic controller objects.</p> </blockquote> <p>The rule in iOS 4 <em>and later</em> remains the same: do not use a UIViewController except as part of a legitimate UIViewController hierarchy, where the view controller's view is in <em>exactly the same</em> hierarchy, as in this diagram from my book:</p> <p><img src="https://i.stack.imgur.com/qNXRA.png" alt="enter image description here"></p> <p>Observe that the view controllers are parent and child <em>and</em> that their views are superview and subview. That is how to use a view controller hierarchy. If you're doing things in iOS 4 that would violate this, don't. Use views but <em>not</em> view controllers.</p>
    singulars
    1. This table or related slice is empty.
    1. POiOS 4.3 Custom Container Programming
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USmatt
    1. USmatt
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POiOS 4.3 Custom Container Programming
      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
    1. COI am implementing my own container view controller that works in a similar way to the UITabBarController. A UIViewController with an NSArray of UIViewControllers, and I have segmented control embedded in the UIViewController in order to swap between the controllers within the array. The issue is when it comes to pushing a new view controller within the children, the children do not have a reference to the parents self.navigationController. However, when using childViewControllers in iOS5 I do, but obviously this isn't supported in 4.3
      singulars
      1. PO
      1. USTim
    2. CORight, well, what my answer above is saying is, don't do that. Don't manipulate view controllers in that way in iOS 4. Just manipulate views, within the view of the legitimate view controller.
      singulars
      1. PO
      1. USmatt
    3. COSuch a frustrating issue as this is a primarily iOS 5+ app, but are being forced to support iOS4 as a secondary issue. How is a UITabController implemented in iOS4 then if you're not supposed to manage multiple VCs within one another?
      singulars
      1. PO
      1. USTim
 

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