I was struggling with the same issue. None of the above solutions worked for me pretty nicely, that is why I decided to do a little investigation and find out how this works. This is what I discovered: When you set the contentSizeForViewInPopover in your view controller it won’t be changed by the popover itself … Read more
I already found the answer Swift 4 let storyBoard : UIStoryboard = UIStoryboard(name: “Main”, bundle:nil) let nextViewController = storyBoard.instantiateViewController(withIdentifier: “nextView”) as! NextViewController self.present(nextViewController, animated:true, completion:nil) Swift 3 let storyBoard : UIStoryboard = UIStoryboard(name: “Main”, bundle:nil) let nextViewController = storyBoard.instantiateViewControllerWithIdentifier(“nextView”) as NextViewController self.presentViewController(nextViewController, animated:true, completion:nil)
A couple of observations: When you instantiate the second view controller, you are calling ViewControllerB(). If that view controller programmatically creates its view (which is unusual) that would be fine. But the presence of the IBOutlet suggests that this second view controller’s scene was defined in Interface Builder, but by calling ViewControllerB(), you are not … Read more
No, this is generally good design, it helps keep your view controllers concise. However you should be using the view controller containment pattern, take a look at the following documentation. Implementing a Container View Controller This is incredibly simple to setup using Interface Builder with Storyboards as well, take a look at the Container View … Read more
I’ve encountered the same issue today. I dug into the topic and it seems that it’s related to the main runloop being asleep. Actually it’s a very subtle bug, because if you have the slightest feedback animation, timers, etc. in your code this issue won’t surface because the runloop will be kept alive by these … Read more
The best thing I have found so far is the WWDC 2011 Session Video Session 102 – Implementing UIViewController Containment.
Solved it! One has to call the designated initializer which in this case is the init with nibName, obviously … init(leftVC:UIViewController, rightVC:UIViewController, gap:Int) { self.leftVC = leftVC self.rightVC = rightVC self.gap = gap super.init(nibName: nil, bundle: nil) setupScrollView() setupViewControllers() }
I had a similar issue recently. I had to manually remove that UITransitionView from the window to fix the problem, then call dismiss on the previous root view controller to ensure its deallocated. The fix is not really very nice but unless you’ve found a better way since posting the question, its the only thing … Read more
As it was specified in one of the answers above you can not use both and custom init method and storyboard. But you still can use a static method to instantiate ViewController from a storyboard and perform additional setup on it. It will look like this: class MemeDetailVC : UIViewController { var meme : Meme! … Read more
I think an example is worth a thousand words. I was working on a library app and wanted to show a nice notepad view that appears when the user wants to add a note. After trying some solutions, I ended up inventing my own custom solution to show the notepad. So when I want to … Read more