Oh - there you go. Assuming that myGameWindowController is the parent window controller that manages myGameViewController, it will create an instance of your LTWMacGameViewController class when it

Looking at the log (and reformatting it a bit): initWithCoder: <LTWMacGameViewController: 0x600003514370> awakeFromNib: <LTWMacGameViewController: 0x600003514370> viewDidLoad:

Hi Jon, I’m not sure what you mean? Do you mean an outlet to the LTWGameViewController in the StartupWindowController? Here’s what I am doing: In

The fact that you've got two instances of your LTWGameViewController certainly sounds like a bug. It's difficult to tell without looking at your whole project, but my guess is that you've got one

Hi Sandor, Yes, LTWGameViewController is a subclass of NSViewController and I set the Class in the Storyboard. When I set a breakpoint in the Set Delegate method it shows the property set ok. Later

I’ve seen this happen if the view controller is instantiated in code and in the NIB (not sure about storyboards) It gets hooked up correctly one time and things are nil in the other case. Are you

Hi, This is the only place the View Controller is instantiated. One thing I’ve notice is that if I set a breakpoint in ViewDidLoad and print self: < LTWMacGameViewController: 0x600003500840> and

Any chance you're reloading your view controller (when starting a new game or whatever) and not subsequently setting the delegates again? - Jon

Hi All, I have a View Controller that is Instantiated in code from a storyboard file: myGameViewController = [myStoryboard instantiateControllerWithIdentifier:kLTWGameMainViewControllerID]; if

Great ! Peter

I usually type out the symbol I’m looking for and then right click and select jump to definition. Sandor

I’m trying to find which files numerical min max types are defined in. Specifically, NSUInteger and its associated types. I have’nt had to look any up for so long, I’ve completely forgotten

Excellent! Glad that was the trick!

Hi, Ahhh, you mean, awakeFromNib in the AppDelegate not the window/view controller. I think I was trying to avoid tying the initialisation to a NIB (in case I ever created it programmatically), but I

There’s a test app attached to demonstrate… Sandor

I see different behaviour. Here’s a test app. No matter what I do, -awakeFromNib is always called first. I tried it both in the AppDelegate, and in the ViewController subclass. Cheers, Sandor

Hi, A little more on this. If I uncheck “Is Initial Controller”, then applicationDidFinishLaunching gets calls as expected. So I put the code back to instantiate it manually and all works as

Hi, This is a Mac project but I will be doing an IOS version too. I’ve tried applicationWillFinishLaunching and applicationDidFinishLaunching, but the View Controller gets control before either

Is this a document-based app or a single-window type app? In my single-window apps, AppDelegate:applicationDidFinishLaunching is called first, and instantiates and displays the main window, so the

If you’re going to look at -init, if it’s an object coming from a NIB then look at overriding -initWithCoder: