Hello Ken,
thanks for your respond. I already read this link and thought that the
NSArrayController "Mailbox" represents this intervening NSController
between the model object and the table view because the table view is
not bound direct to the model or a custom controller. To reformulate
my question - Why is a second intervening NSController in form of an
NSObjectController useful?
Thanks again,
Jochen
Am 04.06.2008 um 03:59 schrieb Ken Thomases:
On Jun 3, 2008, at 6:25 PM, Jochen Moeller wrote:
Both versions run identical, so my question:
Are both approaches equivalent and the NSObjectController is not
really needed or is there a reason/advantage to hook the
NSObjectController between MyController and the NSArrayController ?
See this: http://developer.apple.com/documentation/Cocoa/Conceptual/CocoaBindings/Concepts/WhatAreBindings.html#/
/apple_ref/doc/uid/20002372-177085
In short, yes, it's possible to get away with binding directly to
model objects without an intervening NSController. It's often
better to use such a controller, though, and the link explains why.
Cheers,
Ken
_______________________________________________
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]
