Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When reading Apple’s Cocoa tutorial, the window controller is just a regular class and while understand that this is perfectly fine I suppose, wouldn’t it be better to subclass NSWindowController?
If I get this right, NSWindowController is a convenience class which already has a lot of the functionality required by a window controller implemented, right?
Is there any reason why you would not use this class?
You don’t have to. I’ve sometimes implemented controllers for a window that inherited from
NSObject, if I didn’t really need the added functionality ofNSWindowController.