Why NSWindowController for non-document windows?
Why NSWindowController for non-document windows?
- Subject: Why NSWindowController for non-document windows?
- From: email@hidden (Stefan Haller)
- Date: Tue, 13 Sep 2005 09:34:41 +0200
- Organization: Ableton
I seem to remember having read the recommendation to derive your
controllers for non-document-based windows from NSWindowController too.
I wonder why?
Until now I derived those controllers from NSObject, which seems to have
worked fine so far. Just out of curiosity, I tried changing one to
NSWindowController, seeing what it would buy me; but it only seems to
create problems:
1) The auto-save name defined in the nib is no longer used; I have to
set it programmatically.
2) The auto-saved size and position is only used for the first window I
open; any further windows use the frame defined in the nib. I may be
doing something wrong here, but the auto-save name works just fine
without further work from me if I derive the controller from NSObject.
(See also
<http://www.cocoabuilder.com/archive/message/cocoa/2004/11/9/121184>).
Any insight is greatly appreciated.
--
Stefan Haller
Ableton
http://www.ableton.com/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden