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.
I have an NSView subclass that is used for displaying a custom object. The drawing logic is all in methods on the subclass. There is no view controller associated with this view.
I have added a couple of controls next to this view in Interface Builder that will be used to control the display of the object.
Is it OK to have these controls connected to IBOutlets and IBActions on the view? I know that it’s possible, but is it poor design? Should I be using an NSViewController?
No that is completely fine and it’s how things are supposed to connect together. There is no need to use an
NSViewControlleras it only really helps manage the creation of the view from a.nibfile and it can still only manage one view.