Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>EDIT:</strong> These problems appear to be fixed as of iOS 7.1 / Xcode 5.1.1. (Possibly earlier, as I haven't been able to test all versions. Definitely after iOS 7.0, since I tested that one.) When you create a popover segue from a <code>UIBarButtonItem</code>, the segue makes sure that tapping the popover again hides the popover rather than showing a duplicate. It works right for the new <code>UIPresentationController</code>-based popover segues that Xcode 6 creates for iOS 8, too.</p> <p>Since my solution may be of historical interest to those still supporting earlier iOS versions, I've left it below.</p> <hr> <p>If you store a reference to the segue's popover controller, dismissing it before setting it to a new value on repeat invocations of <code>prepareForSegue:sender:</code>, all you avoid is the problem of getting multiple stacking popovers on repeated presses of the button -- you still can't use the button to dismiss the popover as the HIG recommends (and as seen in Apple's apps, etc.)</p> <p>You can take advantage of ARC zeroing weak references for a simple solution, though:</p> <h3>1: Segue from the button</h3> <p>As of iOS 5, you couldn't make this work with a segue from a <code>UIBarButtonItem</code>, but you can on iOS 6 and later. (On iOS 5, you'd have to segue from the view controller itself, then have the button's action call <code>performSegueWithIdentifier:</code> after checking for the popover.)</p> <h3>2: Use a reference to the popover in <code>-shouldPerformSegue...</code></h3> <pre><code>@interface ViewController @property (weak) UIPopoverController *myPopover; @end @implementation ViewController - (void)prepareForSegue:(UIStoryboardSegue *)segue sender:(id)sender { // if you have multiple segues, check segue.identifier self.myPopover = [(UIStoryboardPopoverSegue *)segue popoverController]; } - (BOOL)shouldPerformSegueWithIdentifier:(NSString *)identifier sender:(id)sender { if (self.myPopover) { [self.myPopover dismissPopoverAnimated:YES]; return NO; } else { return YES; } } @end </code></pre> <h3>3: There's no step three!</h3> <p>The nice thing about using a zeroing weak reference here is that once the popover controller is dismissed -- whether programmatically in <code>shouldPerformSegueWithIdentifier:</code>, or automatically by the user tapping somewhere else outside the popover -- the ivar goes to <code>nil</code> again, so we're back to our initial state.</p> <p>Without zeroing weak references, we'd have to also:</p> <ul> <li>set <code>myPopover = nil</code> when dismissing it in <code>shouldPerformSegueWithIdentifier:</code>, and</li> <li>set ourself as the popover controller's delegate in order to catch <code>popoverControllerDidDismissPopover:</code> and also set <code>myPopover = nil</code> there (so we catch when the popover is automatically dismissed).</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POHow to Dismiss a Storyboard Popover
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USrickster
    1. USrickster
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to Dismiss a Storyboard Popover
      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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COProps to @wcochran for help figuring this out.
      singulars
      1. PO
      1. USrickster
    2. CO+1 great answer, thank you! Love how the ivar is declared in the @implementation
      singulars
      1. PO
      1. USDan Fairaizl
    3. COThanks. Encapsulation is good! (In fact, Apple's latest version of the primary [ObjC language documentation](http://developer.apple.com/library/ios/documentation/Cocoa/Conceptual/ObjectiveC/Chapters/ocDefiningClasses.html) treats implementation ivars as the default.)
      singulars
      1. PO
      1. USrickster
 

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