Why can't I call the default super.init() on UIViewController in Swift?
Solution 1:
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.
Solution 2:
Another nice solution is to declare your new initializer as a convenience
initializer as follows:
convenience init( objectId : NSManagedObjectID ) {
self.init()
// ... store or user your objectId
}
If you declare no designated initializers in your subclass at all, they are inherited automatically and you are able to use self.init()
within your convenience initializer.
In case of UIViewController the default init method will call init(nibName nibNameOrNil: String!, bundle nibBundleOrNil: NSBundle!)
with nil
for both arguments (Command-Click on UIViewController will give you that info).
TL;TR: If you prefer to programmatically work with UIViewController
s here is a complete working example that adds a new initializer with a custom argument:
class MyCustomViewController: UIViewController {
var myString: String = ""
convenience init( myString: String ) {
self.init()
self.myString = myString
}
}
Solution 3:
To improve the occulus's answer:
init() {
super.init(nibName: nil, bundle: nil)
}