You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my specific case, I have the SWRevealViewController as my root, which embeds a navigation controller as the front view controller, and then a long tree of view controllers where, eventually, one shows a modal view controller.
In iOS 7, unwind segue is triggered, it calls the method -(UIViewController *)viewControllerForUnwindSegueAction:fromViewController:withSender: on the presenting view controller, which returns self. This allows the view controller to define who should handle creating the segue for unwinding.
In iOS 8, this is no longer the case. The exit segue is now delegated to the root view controller, which in my case, would be the SWRevealViewController. The SWRevealViewController does not forward the message to the front view controller, therefore, the exit segue never gets created.
I'll be creating a fork and submitting a pull request to fix this, but I assume there should be some discussion on how you would like the logic to flow. I have how I would imagine it works.
The text was updated successfully, but these errors were encountered:
In my specific case, I have the SWRevealViewController as my root, which embeds a navigation controller as the front view controller, and then a long tree of view controllers where, eventually, one shows a modal view controller.
In iOS 7, unwind segue is triggered, it calls the method
-(UIViewController *)viewControllerForUnwindSegueAction:fromViewController:withSender:
on the presenting view controller, which returns self. This allows the view controller to define who should handle creating the segue for unwinding.In iOS 8, this is no longer the case. The exit segue is now delegated to the root view controller, which in my case, would be the SWRevealViewController. The SWRevealViewController does not forward the message to the front view controller, therefore, the exit segue never gets created.
I'll be creating a fork and submitting a pull request to fix this, but I assume there should be some discussion on how you would like the logic to flow. I have how I would imagine it works.
The text was updated successfully, but these errors were encountered: