On Thu, Jan 22, 2009 at 1:11 PM, Cormac Daly wrote:
> I had created a custom class for the window controller in Interface Builder,
> but I got rid of it and hooked up all the outlets via File's Owner instead.
> I'm not sure exactly how this worked but it did!
You don't create classes in IB, you i
Thank you to everyone who replied to this query: it is now resolved.
I had created a custom class for the window controller in Interface Builder,
but I got rid of it and hooked up all the outlets via File's Owner instead.
I'm not sure exactly how this worked but it did!
Thanks again,
Cormac
On T
On Thu, Jan 22, 2009 at 2:44 AM, Cormac Daly wrote:
> Any ideas? Is there a problem in the ordering somewhere? Its probably
> something very basic but I'm stumped!
You are subclassing NSWindowController and NSWindowController will
call windowDidLoad after the nib it loads is fully instantiated a
Did you make the connections in IB?
You need to do that on top of adding the outlets in code.
Joseph Crawford
On Jan 22, 2009, at 5:44 AM, Cormac Daly wrote:
Hi list,
I've added a new window to my application and have written a window
controller class. Everything is going fine, except for the
Hi list,
I've added a new window to my application and have written a window
controller class. Everything is going fine, except for the fact that
when initialising the window, none of my IBOutlets are responding to
methods called on them. This is the case in both the init and
windowDidLoad methods
