Home/ Questions/Q 523081
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T08:25:14+00:00

For instance: Create a new UIVC using initWithNibName, using nib-v1 Display it, e.g. using

  • 0

For instance:

  1. Create a new UIVC using initWithNibName, using “nib-v1”
  2. Display it, e.g. using [(UINavigationController) nav pushViewController: myVC]
  3. Change the NIB that myVC is using to “nib-v2”

So far as I can see, this is the “correct” approach to app-design for a lot of apps, when paging through information where you need two slightly different UI screens for the info being displayed.

For instance, most of your pages are text, but some of them have an image too (think of an RSS reader, where some RSS entries have text + image, some are text only).

I’ve dealt with this previously by having one NIB file with a second, invisible, named UIView instance that I layered over the top of the first one, and switched on/off depending on on context, using the “hidden” flag.

But this is clearly wrong, and wastes memory.

However, I cannot see an obvious way to “reload” the view from the NIB file. I’m guessing I want to somehow reproduce the magic that initWithNibName does?

I suspect this is possible, but I’m sure that if you do it “the wrong way” then the app will simply crash horribly.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I agree with Rob, but if you really want to mess with swapping nib’s (which is bad as it can easily lead to dangling pointers and the like), you could maybe load the view from the new nib with NSBundle‘s - (NSArray *)loadNibNamed:(NSString *)name owner:(id)owner options:(NSDictionary *)options method and do the view swapping yourself.

    You should rather use different view controllers for different types of content. If they only differ slightly, you can still consider creating one base class and subclassing the different variations.

    • 0