NSViewController Class Reference

Discussion

A commit is denied if the receiver fails to apply the changes to the model object, perhaps due to a validation error.

Discussion

The receiver must have been registered as the editor of an object using objectDidBeginEditing:, and has not yet been unregistered by a subsequent invocation of objectDidEndEditing:. When the committing has either succeeded or failed, send the delegate the message specified by didCommitSelector.

The didCommitSelector method must have the following method signature:.

- (void)editor:(id)editor didCommit:(BOOL)didCommit contextInfo:(void  *)contextInfo

If an error occurs while attempting to commit, for example if key-value coding validation fails, an implementation of this method should typically send the receiver’s view apresentError:modalForWindow:delegate:didPresentSelector:contextInfo: message, specifying the view's containing window.

You may find this method useful in some situations when you want to ensure that pending changes are applied before a change in user interface state. For example, you may need to ensure that changes pending in a text field are applied before a window is closed. See also commitEditing which performs a similar function but which allows you to handle any errors directly, although it provides no information beyond simple success/failure.

Discussion

The NSViewController object looks for the nib file in the bundle's language-specific project directories first, followed by the Resources directory.

The specified nib should typically have the class of the file's owner set to NSViewController, or a custom subclass, with the view outlet connected to a view.

If you pass in a nil for nibNameOrNil then nibName will return nil and loadView will throw an exception; in this case you must invoke setView: before view is invoked, or override loadView.

Discussion

The default implementation of this method invokes nibName and nibBundle and then uses the NSNib class to load the nib with the receiver as the file's owner. If the view outlet of the file's owner in the nib is properly connected, the regular nib loading machinery will send the receiver a setView: message.

Discussion

The default implementation returns whatever value was passed to the initializer.

Discussion

The default implementation returns whatever value was passed to the initializer.

Discussion

This class is key-value coding and key-value observing compliant for representedObject so when you use it as the file's owner of a view's nib you can bind controls to the file's owner using key paths that start with representedObject.

Discussion

The default implementation of this method doesn't copy the passed-in object, it retains it. In another words, representedObject is a to-one relationship, not an attribute.

This class is key-value coding and key-value observing compliant for representedObject so when you use it as the file's owner of a view's nib you can bind controls to the file's owner using key paths that start with representedObject.

Discussion

NSViewController does not use the title property directly. This property is here because so many anticipated uses of this class will involve letting the user choose among multiple named views using a pulldown menu or some other user interface.

This class is key value coding and key value compliant for this property.

Discussion

You can invoke this method immediately after creating the object to specify a view that's created in a different manner than the receiver's default implementation would provide.

Discussion

NSViewController does not use the title property directly. This property is here because so many anticipated uses of this class will involve letting the user choose among multiple named views using a pulldown menu or some other user interface.

This class is key value coding and key value compliant for this property.

Discussion

The default implementation of this method first invokes loadView if the view hasn't been set yet.