Home/ Questions/Q 6615267
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T20:26:29+00:00

Let say I have a NSObject AppController:NSObject. Using IB, I drag an NSObject control

  • 0

Let say I have a NSObject AppController:NSObject. Using IB, I drag an NSObject control into MainMenu.xib and points the class to AppController. Since MainMenu.xib is loaded once and objects inside MainMenu.xib are in memory for the life of the app, does it make the AppController object a singleton?

Then I can drag an IBOutlet to AppDelegate to access this singleton object. This looks like a quick way. Is this a good practice or to be discouraged?

The standard method I supposed is to add a static AppController *sharedInstance inside the class and use a +(AppController *)sharedAppController for access.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    No, it’s not a singleton because nothing stops you from creating another instance of the same class in code.

    It’s just a convenient way to create a single instance.

    and objects inside MainMenu.xib are in memory for the life of the app

    This is not true. If nobody retains these objects (or holds a strong reference to them under GC), they will get deallocated. This is true. See Peter Hosey’s comment below.

    • 0