I thought that I should never call [super loadView] but something is confusing me.
In description of loadView (UIViewController Class Reference) it is said that “Your custom implementation of this method should not call super.”,
but in ZoomingPDFViewer example that they gave, loadView implementation (ZoomingPDFViewerViewController) is calling [super loadView].
I have tried to call it from my loadView method and it works ok, but I just don’t understand then what does it mean to not call super.
You definitely should not be calling
[super loadView]. I’d say you found a bug in the ZoomingPDFViewer example.You override
loadViewwhen you want to programatically create the view hierarchy for your view controller (not using a xib).As you pointed out, the docs clearly state that you should not call super.
I assume this is to avoid loading both from a xib and programatically creating a view as this method is used by the base to load a view from a xib:
Note also that even if during allocation of your
UIViewControllerobject you pass nil for the nibNameOrNil parameter that theUIViewControllerimplementation ofloadViewwill try to load any xib with the associated class name in it.The real intent of this method is to give you full control of building the view hierarchy without relying on the built in xib loading mechanism.:
Personally, I override
loadViewif: 1.) The xib I would make for it is really trivial or 2.) The layout of the control is very dynamic, so creating a xib with a static layout has little benefit.