Hi mmalc,
Actually this is exactly how I got it to work...
I guess the reason why I wanted to add an object controller in the first place is that the details pane changes depending on the selection in the tree view (I got different views for "table inspector", "view inspector" etc, each with it's own detail fields). I thought that having a dedicated object controller for each pane would be the way to go, each controller only presenting the relevant data to the pane.
I guess I simply underestimated (yet again!) the flexibility of bindings !
Thanks for your help !
Alain
On Wednesday, August 29, 2007, at 09:03PM, "mmalc crawford" <email@hidden> wrote:
>
>On Aug 29, 2007, at 8:49 AM, Alain Schartz wrote:
>
>> I suppose the main problem resides in the fact that the entities
>> used by the treeController ("TreeNodes") are different from the
>> entities I want to display in my details panel ("Table"); every
>> bindings combination I tried either resulted in "selector not
>> recognized" or KVO error messages (or simply nothing happening at
>> all). So my question is, how do I tell my NSObjectController to take
>> the selection.name from NSTreeController (and thus "casting" the
>> "TreeNode" entity to the details-pane "Table" entity) ?
>> Since both have a "name" attribute methinks this should somehow be
>> feasable?
>>
>In what sense should the NSObjectController "take the selection.name
>from NSTreeController"?
>It's not clear why you need an object controller for the selection
>anyway?
>Why can you not simply bind the text fields to
>[NSTreeController].selection.attributeName?
>
>mmalc
>
>
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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/email@hidden
This email sent to email@hidden
