Re: Choosing view controller for segue
Re: Choosing view controller for segue
- Subject: Re: Choosing view controller for segue
- From: Quincey Morris <email@hidden>
- Date: Thu, 15 Jun 2017 14:51:20 -0700
On Jun 15, 2017, at 14:06 , Steve Mills <email@hidden> wrote:
>
> I'm not sure how to add a 2nd one from a common source. When I try
> right-dragging from the embedding view to the 2nd target VC, it deletes the
> segue already wired to the 1st target VC.
Well, you can’t have a second embedding if it’s an embedding segue.
Typically, if it’s already an embedding, you can simply segue from one embedded
VC to another (and back again via unwinding).
If it’s already a little more structured then that, then you can introduce an
extra level of containment. For example, if you want to display one of two
different VCs in the detail view of a split view controller, you shouldn’t put
either of the 2 sub-VCs as the detail VC. Instead, put a plain VC there, and
replace its view with a “container” view, in which can embed one of the
sub-VCs, with a segue from that sub-VC to the other one.
(Actually, in the split view controller case, you can simply replace the detail
VC, since UISplitViewController has API for that. But if you actually want a
segue, perhaps for the animation, then you have to go the containment route.)
Using a tab-less tab view is also a way to go, but it’s hitting it with a
bigger hammer than you really need.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden