In your Storyboard, you can embed a ViewController in a Navigation Controller by selecting the View Controller and then picking from the menu at the top Editor->Embed In->Navigation Controller. From another view controller, you control drag to this Navigation controller to set up the modal segue. You can also control drag to the original View … Read more
After performSegueWithIdentifier:sender: your view controler will call – (void)prepareForSegue:(UIStoryboardSegue *)segue sender:(id)sender assuming your new view controller has some propertys to set: if ([[segue identifier] isEqualToString:@”NextView”]) { MyViewController *myVC = [segue destinationViewController]; myVC.propertyToSet = // set your properties here }
I had a hard time following the accepted answer so here is more detail. Given the photo below on view controller C you can “exit” back to any view controller in the segue path. ViewController A you can write: – (IBAction)done:(UIStoryboardSegue *)segue { // Optional place to read data from closing controller } ViewController B … Read more
You aren’t using the modal segues correctly. The way you have implemented it, you are creating a new instance of each view controller when you segue instead of returning to the instance you came from. That is why your memory usage continues to increase. Before iOS 6, the correct way to handle this was to: … Read more
To expand on the various segues above, this is my solution. It has the following advantages: Can work anywhere in the view stack, not just the top view (not sure if this is realistically ever needed or even technically possible to trigger, but hey it’s in there). It doesn’t cause a pop OR transition to … Read more
I had this same problem and actually my problem was that I was calling WRONG: [self.navigationController performSegueWithIdentifier:@”ShowVerify” sender:self]; instead of CORRECT: [self performSegueWithIdentifier:@”ShowVerify” sender:self]; so check that you are calling correct performSegueWithIdentifier method 🙂
So basically the segue was freezing because of the UITextView‘s I was using in the destinationViewController. The following fixed the issue: Delete all UITextView‘s Add new UITextView’s you must leave the default lorem imposed text and change this programmatically in the viewDidLoad() This was the fix for me, and from the research I have done … Read more
I was able to fix it by running “clean” under the “Product” menu in Xcode, and resetting the contents and settings in the simulator.
Here is how to set up a segue so that it can be called programmatically. Control drag from the ViewController icon in the first view controller to the second view controller. Click on the segue arrow between the two view controllers, and in the Attributes Inspector on the right, give the segue an Identifier (tableau … Read more
This seems to be due to a problem in the UITableViewController subclass template. It comes with a version of the prepareForSegue method that would require you to unwrap the segue. Replace your current prepareForSegue function with: override func prepareForSegue(segue: UIStoryboardSegue!, sender: AnyObject!) { if (segue.identifier == “Load View”) { // pass data to next view … Read more