> On 6 May 2016, at 20:49, Roland King <r...@rols.org> wrote: > > I have a navigation controller as the detail pane of a UISplitView (pretty > much right from the standard splitview template). > > Now I want to push another view onto that stack. I have the view, I’ve > dragged out a segue to connect it up however none of the available ‘adaptive > segues’ do a ‘push’. Even the ‘Show (Push)’ one doesn’t push, it replaces the > view entirely and removes the nav controller. > > If I use the deprecated ‘push’ segue, then it pushes, but it’s deprecated and > gives me a handy yellow triangle warning me of such. > > Am I falling foul of the splitview controller’s adaptation here somehow? I’m > a little hazy on the way adaptive segues work but it feels like the ‘show’ is > being sent up to and interpreted by the splitview controller and doing a > replace on the detail pane instead of a push. But it could be something > entirely different. > > I could hook the button up to make the new view controller and push it > instead of using a segue, but I’d rather not. Is there a way I can make > ‘Show’ do a ‘Push’?
As usual, asking the question made me think about it and get the answer. Override showDetailViewController:sender: to do the push (or something else if appropriate in that adaptation which in this case is always push). If not, the targetViewController is found which is the splitview controller which does a detail pane replace. This stuff sometimes almost makes sense, if you don’t think about it too hard. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
