Re: windowcontroller neccessary?
Re: windowcontroller neccessary?
- Subject: Re: windowcontroller neccessary?
- From: Mike Ferris <email@hidden>
- Date: Sat, 11 Jan 2003 10:53:07 -0800
An NSWindowController gives you some nice nib-management features. For
example, an NSWindowController knows about all the top-level objects in
the nib it loads and it will release them when it goes away. Without
this you have to be sure to create outlets to all the top-level objects
and release them yourself or you'll leak.
The NSWindowController for a window does not have to be the window's
delegate. A window can have both a windowController and a delegate.
It is often the case that people make their windowControllers be the
window's delegate as well, however.
You do not have to have an NSWindowController, and if you do have one
it can be a subclass or just a plain NSWindowController (although
usually it is a subclass).
If you are using NSDocument then the document windows will always have
a windowController. For non-document windows, you can do what you
like, but NSWindowController is a really good class to start with for
your File's Owner.
Mike
Begin forwarded message:
From: daniel oberhoff <email@hidden>
Date: Sat Jan 11, 2003 6:08:00 AM US/Pacific
To: cocoa-dev <email@hidden>
Subject: windowcontroller neccessary?
hi folks!
question: is there any forcing reason to ever user NSWindowControler
as a superclass? coz its not problem using any class as a delegate for
a window, you just have to implement the right message responders...
daniel oberhoff
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.