and, to add another addendum..
in the case of some controls (text fields and text views for example)
not using a controller _can_ cause you problems, and your app to lose
data.
anything that doesn't immediately send its value to from a control to
the data model upon editing requires some protocol support that your
data object just isn't going to have by default. these protocols
ensure that when a view or object resigns its active status that the
values are updated appropriately.
On Apr 28, 2008, at 1:05 AM, William Turner wrote:
You aren't strictly _required_ to use an NSObjectController (or
other NSController subclass), but in practice it is generally better
to do so. Yes, you can bind your views directly to your controller
classed, but that's not really the ideal pattern
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
