Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Dragging onto the exit of the viewcontroller not working

I have looked for this problem everywhere. I know how the unwind scene works. I have implemented the following code in the A VC

-(IBAction)returned:(UIStoryboardSegue *)segue {
try.text = @"Returned from Scene 1";
}

But when I go to my B VC(Which is the VC I want to go back to A VC from) and ctrl drag a button onto the exit at the bottom it will not allow me to. And no function pops up in the exits option. Anyone else had this issue or can help?

like image 223
Sfocker Avatar asked Mar 19 '13 21:03

Sfocker


People also ask

How do I close ViewController?

If you use push, you should dismiss it with the pop method of the navigation controller.


3 Answers

To set up an unwind segue, you should

  1. Set up your two scenes with the standard modal or push segue between them:

    enter image description here

  2. Define the custom classes for those two scenes to be your respective view controllers.

  3. Implement the action in the .m for view controller A:

    - (IBAction)unwindToA:(UIStoryboardSegue *)segue
    {
        //returning to A
    }
    
  4. Then you can create a segue in B by control-dragging (or right-click-dragging) from some control down to the exit outlet in the bar below scene B:

    enter image description here

  5. And if everything above is configured correctly, you will now see your unwind segue listed in a popover:

    enter image description here

like image 88
Rob Avatar answered Oct 19 '22 16:10

Rob


To make Exit outlet active, add this code to viewController. Now you should be able to ctrl-drag to exit outlet. It is actually quite odd, that there should be empty method to make it work.

swift
@IBAction func unwindSegue(unwindSegue:UIStoryboardSegue) 

objC
- (IBAction)unwindSegue:(UIStoryboardSegue *)sender;
like image 23
Mantas Laurinavičius Avatar answered Oct 19 '22 16:10

Mantas Laurinavičius


I also had a problem with this even though everything was set up correctly. Eventually I tried closing the project and reopening it and that did the trick. Must have been some bug in Xcode.

This doesn't seem to have been the cause of your problem but I thought I'd add the answer in case someone else has the same problem.

like image 32
LoPoBo Avatar answered Oct 19 '22 18:10

LoPoBo