This is something I still don't quite understand: Why should I bind to an NSObjectController bound to an object, instead of just binding to the object itself? Say for instance that I bind the values of a bunch of controls to [File's Owner].value1, [File's Owner].value2, [File's Owner].value3.... Should I be using an NSObjectController bound to File's Owner, and then bind the controls to the object controller? If so, why?
What if I instead bound the controls to [File's Owner].someObj.value1, [File's Owner].someObj.value2, [File's Owner].someObj.value3, etc.? Malcolm briefly alludes to created an NSObjectController bound to [File's Owner].someObj and then binding the controls to [Object Controller].value[N] instead. Why would I do this though? Simply for brevity?
What is it that NSObjectController offers me? Thanks! -- Seth Willits _______________________________________________ Cocoa-dev mailing list ([email protected]) 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]
