I've created a popover from a UIBarButtonItem
using Xcode Storyboards (so there's no code) like this:
Presenting the popover works just fine. However, I can't get the popover to disappear when I tap the UIBarButtonItem
that made it appear.
When the button is pressed (first time) the popover appears. When the button is pressed again (second time) the same popover appears on top of it, so now I have two popovers (or more if I continuer pressing the button). According to the iOS Human Interface Guidelines I need to make the popover appear on the first tap and disappear on the second:
Ensure that only one popover is visible onscreen at a time. You should not display more than one popover (or custom view designed to look and behave like a popover) at the same time. In particular, you should avoid displaying a cascade or hierarchy of popovers simultaneously, in which one popover emerges from another.
How can I dismiss the popover when the user taps the UIBarButtonItem
for a second time?
Best Answer
EDIT: 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
UIBarButtonItem
, the segue makes sure that tapping the popover again hides the popover rather than showing a duplicate. It works right for the newUIPresentationController
-based popover segues that Xcode 6 creates for iOS 8, too.Since my solution may be of historical interest to those still supporting earlier iOS versions, I've left it below.
If you store a reference to the segue's popover controller, dismissing it before setting it to a new value on repeat invocations of
prepareForSegue:sender:
, 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.)You can take advantage of ARC zeroing weak references for a simple solution, though:
1: Segue from the button
As of iOS 5, you couldn't make this work with a segue from a
UIBarButtonItem
, 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 callperformSegueWithIdentifier:
after checking for the popover.)2: Use a reference to the popover in
-shouldPerformSegue...
3: There's no step three!
The nice thing about using a zeroing weak reference here is that once the popover controller is dismissed -- whether programmatically in
shouldPerformSegueWithIdentifier:
, or automatically by the user tapping somewhere else outside the popover -- the ivar goes tonil
again, so we're back to our initial state.Without zeroing weak references, we'd have to also:
myPopover = nil
when dismissing it inshouldPerformSegueWithIdentifier:
, andpopoverControllerDidDismissPopover:
and also setmyPopover = nil
there (so we catch when the popover is automatically dismissed).