In the XIB, I changed the "File's Owner" class to SomeView (in the identity inspector). I created a UIView outlet in SomeView. swift, linking it to the top level view in the XIB file (named it "view" for convenience). I then added other outlets to other controls in the XIB file as needed.
In fact, the acronym "NIB" comes from "NeXTSTEP Interface Builder", and "XIB" from "Xcode Interface Builder". NIBs and XIBs are effectively the same thing: XIBs are newer and are used while you're developing, whereas NIBs are what get produced when you create a build.
There is also an easier way to access the view instead of dealing with the nib as an array.
1) Create a custom View subclass with any outlets that you want to have access to later. --MyView
2) in the UIViewController that you want to load and handle the nib, create an IBOutlet property that will hold the loaded nib's view, for instance
in MyViewController (a UIViewController subclass)
@property (nonatomic, retain) IBOutlet UIView *myViewFromNib;
(dont forget to synthesize it and release it in your .m file)
3) open your nib (we'll call it 'myViewNib.xib') in IB, set you file's Owner to MyViewController
4) now connect your file's Owner outlet myViewFromNib to the main view in the nib.
5) Now in MyViewController, write the following line:
[[NSBundle mainBundle] loadNibNamed:@"myViewNib" owner:self options:nil];
Now as soon as you do that, calling your property "self.myViewFromNib" will give you access to the view from your nib!
Thank you all. I did find a way to do what I wanted.
UIView
with the IBOutlet
s you need.UIViewController
(No custom subclass, but the "real" one). The File Owner's view is connected to the main view and its class is declared as the one from step 1).IBOutlet
s.The DynamicViewController
can run its logic to decide what view/xib to load. Once its made the decission, in the loadView
method put something like this:
NSArray* nibViews = [[NSBundle mainBundle] loadNibNamed:@"QPickOneView"
owner:self
options:nil];
QPickOneView* myView = [ nibViews objectAtIndex: 1];
myView.question = question;
That's it!
The main bundle's loadNibNamed
method will take care of initializing the view and creating the connections.
Now the ViewController can display a view or another depending on the data in memory, and the "parent" screen doesn't need to bother with this logic.
I'm not sure what some of the answers are talking about, but I need to put this answer here for when I search in Google next time. Keywords: "How to load a UIView from a nib" or "How to load a UIView from an NSBundle."
Here's the code almost 100% straight up from the Apress Beginning iPhone 3 book (page 247, "Using The New Table View Cell"):
- (void)viewDidLoad {
[super viewDidLoad];
NSArray *bundle = [[NSBundle mainBundle] loadNibNamed:@"Blah"
owner:self options:nil];
Blah *blah;
for (id object in bundle) {
if ([object isKindOfClass:[Blah class]]) {
blah = (Blah *)object;
break;
}
}
assert(blah != nil && "blah can't be nil");
[self.view addSubview: blah];
}
This supposes you have a UIView
subclass called Blah
, a nib called Blah
which contains a UIView
which has its class set to Blah
.
#import "NSObject+LoadFromNib.h"
@implementation NSObject (LoadFromNib)
+ (id)loadFromNib:(NSString *)name classToLoad:(Class)classToLoad {
NSArray *bundle = [[NSBundle mainBundle] loadNibNamed:name owner:self options:nil];
for (id object in bundle) {
if ([object isKindOfClass:classToLoad]) {
return object;
}
}
return nil;
}
@end
extension UIView {
class func loadFromNib<T>(withName nibName: String) -> T? {
let nib = UINib.init(nibName: nibName, bundle: nil)
let nibObjects = nib.instantiate(withOwner: nil, options: nil)
for object in nibObjects {
if let result = object as? T {
return result
}
}
return nil
}
}
And an example in use:
class SomeView: UIView {
class func loadFromNib() -> SomeView? {
return self.loadFromNib(withName: "SomeView")
}
}
For all those that need to manage more than one instance of the custom view, that is an Outlet Collection, I merged and customized the @Gonso, @AVeryDev and @Olie answers in this way:
Create a custom MyView : UIView
and set it as "Custom Class" of the root UIView
in the desired XIB;
Create all outlets you need in MyView
(do it now because after point 3 the IB will propose you to connect outlets to the UIViewController
and not to the custom view as we want);
Set your UIViewController
as "File's Owner" of the custom view XIB;
In the UIViewController
add a new UIViews
for each instance of MyView
you want, and connect them to UIViewController
creating an Outlet Collection: these views will act as "wrapper" views for the custom view instances;
Finally, in the viewDidLoad
of your UIViewController
add the following lines:
NSArray *bundleObjects; MyView *currView; NSMutableArray *myViews = [NSMutableArray arrayWithCapacity:myWrapperViews.count]; for (UIView *currWrapperView in myWrapperViews) { bundleObjects = [[NSBundle mainBundle] loadNibNamed:@"MyView" owner:self options:nil]; for (id object in bundleObjects) { if ([object isKindOfClass:[MyView class]]){ currView = (MyView *)object; break; } } [currView.myLabel setText:@"myText"]; [currView.myButton setTitle:@"myTitle" forState:UIControlStateNormal]; //... [currWrapperView addSubview:currView]; [myViews addObject:currView]; } //self.myViews = myViews; if need to access them later..
I would use UINib to instantiate a custom UIView to be reused
UINib *customNib = [UINib nibWithNibName:@"MyCustomView" bundle:nil];
MyCustomViewClass *customView = [[customNib instantiateWithOwner:self options:nil] objectAtIndex:0];
[self.view addSubview:customView];
Files needed in this case are MyCustomView.xib, MyCustomViewClass.h and MyCustomViewClass.m
Note that [UINib instantiateWithOwner]
returns an array, so you should use the element which reflects the UIView you want to re-use. In this case it's the first element.
You should not be setting the class of your view controller to be a subclass of UIView
in Interface Builder. That is most definitely at least part of your problem. Leave that as either UIViewController
, some subclass of it, or some other custom class you have.
As for loading only a view from a xib, I was under the assumption that you had to have some sort of view controller (even if it doesn't extend UIViewController
, which may be too heavyweight for your needs) set as the File's Owner in Interface Builder if you want to use it to define your interface. I did a little research to confirm this as well. This is because otherwise there would be no way to access any of the interface elements in the UIView
, nor would there be a way to have your own methods in code be triggered by events.
If you use a UIViewController
as your File's Owner for your views, you can just use initWithNibName:bundle:
to load it and get the view controller object back. In IB, make sure you set the view
outlet to the view with your interface in the xib. If you use some other type of object as your File's Owner, you'll need to use NSBundle
's loadNibNamed:owner:options:
method to load the nib, passing an instance of File's Owner to the method. All its properties will be set properly according to the outlets you define in IB.
You can also use UIViewController's initWithNibName instead of loadNibNamed. It is simpler, I find.
UIViewController *aViewController = [[UIViewController alloc] initWithNibName:@"MySubView" bundle:nil];
[self.subview addSubview:aViewController.view];
[aViewController release]; // release the VC
Now you just have to create MySubView.xib and MySubView.h/m. In MySubView.xib set the File's Owner class to UIViewController and view class to MySubView.
You can position and size of the subview
using the parent xib file.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With