If your app’s root view controller is a UINavigationController you can do this: ((UINavigationController*)appDelegate.window.rootViewController).visibleViewController; Similarly, if it’s a UITabBarController you can do this: ((UITabBarController*)appDelegate.window.rootViewController).selectedViewController; Of course, explicit casting like this is dirty. Better would be to capture the reference yourself using strong types.
You could use the UINavigationController‘s viewControllers property: @property(nonatomic, copy) NSArray *viewControllers Discussion: The root view controller is at index 0 in the array, the back view controller is at index n-2, and the top controller is at index n-1, where n is the number of items in the array. https://developer.apple.com/documentation/uikit/uinavigationcontroller You could use that to … Read more
Try This : self.view.window?.rootViewController?.dismiss(animated: true, completion: nil) it should dismiss all view controllers above the root view controller. If that doesn’t work than you can manually do that by running a while loop like this. func dismissViewControllers() { guard let vc = self.presentingViewController else { return } while (vc.presentingViewController != nil) { vc.dismiss(animated: true, completion: … 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
The designated initialiser for UIViewController is initWithNibName:bundle:. You should be calling that instead. See http://www.bignerdranch.com/blog/real-iphone-crap-2-initwithnibnamebundle-is-the-designated-initializer-of-uiviewcontroller/ If you don’t have a nib, pass in nil for the nibName (bundle is optional too). Then you could construct a custom view in loadView or by adding subviews to self.view in viewDidLoad, same as you used to.
if you are trying to access the rootViewController you set in your appDelegate. try this: Objective-C YourViewController *rootController = (YourViewController*)[[(YourAppDelegate*) [[UIApplication sharedApplication]delegate] window] rootViewController]; Swift let appDelegate = UIApplication.sharedApplication().delegate as AppDelegate let viewController = appDelegate.window!.rootViewController as YourViewController Swift 3 let appDelegate = UIApplication.shared.delegate as! AppDelegate let viewController = appDelegate.window!.rootViewController as! YourViewController Swift 4 & 4.2 … Read more
You are getting this error because you have the code in the wrong place in the class so move it to any function or in viewDidLoad method. You can have only declarations in class scope, not expressions to be executed. And it will work fine. EDIT: In your second UIViewController just read highScore from NSUserDefaults … Read more
This is not confusing at all – in fact, this comes up all the time. The way this works in model-view-controller systems is that you set up a model class, make it a singleton, and add references to that singleton in all controllers that need to share the data. Model.h @interface Model : NSObject @property … Read more
When a view controller is being initialized, inside the initWithNibName method, the views that reside in the view controller aren’t yet initialized and you can’t set their properties yet. Do whatever you need that is view based in the “viewDidLoad” method.
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