\n
My understanding is that the relationship segue between nav controller and destination VC can only be connected to one source VC? Every time I fixed one, the other broke.
\nAll my attempt to implement prepare for segue generated fatal init coder errors.
\nRemoving the navigation controller and implementing two @IBSegueAction func's got the segues working but removed the required navigation bar (and its save, cancel buttons).
\nI'm sure I'm missing something simple to elegantly create this workflow. But I can't find it.
\nI'm using Xcode 14.3 and building in UIKit.
\n","author":{"@type":"Person","name":"Phil"},"upvoteCount":0,"answerCount":1,"acceptedAnswer":null}}Reputation: 71
I'm searching for what I believe must be the simple solution to showing (modal) the same destination view controller (an edit screen - with navigation controller and nav bar) from two source view controllers: 1) the root list, and 2) the view item screen.
Here's the sort of thing I mean:
My understanding is that the relationship segue between nav controller and destination VC can only be connected to one source VC? Every time I fixed one, the other broke.
All my attempt to implement prepare for segue generated fatal init coder errors.
Removing the navigation controller and implementing two @IBSegueAction func's got the segues working but removed the required navigation bar (and its save, cancel buttons).
I'm sure I'm missing something simple to elegantly create this workflow. But I can't find it.
I'm using Xcode 14.3 and building in UIKit.
Upvotes: 0
Views: 272
Reputation: 77690
Many different ways to handle this type of navigation / flow.
One approach...
Instead of embedding your "Edit" table view controller in (another) navigation controller, add a UINavigationBar
to the table view controller.
Now you can present
it from
This is basically how it would look:
Really, really quick example project: https://github.com/DonMag/NavApproach
Upvotes: 0