Custom View for hierarchy -- NSTreeController or Data Source?
Custom View for hierarchy -- NSTreeController or Data Source?
- Subject: Custom View for hierarchy -- NSTreeController or Data Source?
- From: John Velman <email@hidden>
- Date: Sat, 10 Dec 2011 15:46:18 -0800
- Mail-followup-to: John Velman <email@hidden>, Cocoa Development <email@hidden>
(Using Xcode 4.2, writing for OS X Lion)
I have a hierarchy of stuff I want to display (at the same time) in both
outline view and a custom view. Sort of analagous to the Buck and Yacktman
(Cocoa Design Patterns) example in CH. 29, but with Outline instead of
Table. I'll most likely have a detail view available also.
I've only used NSTreeController with a single outline view before. Now I
have found that "arrangedObjects" aren't what one would like them to be.
Also found that (for some reason) all the 'canInsert' and it's relatives
have value NO (for some reason I can't find (or find with google)). So so
far, it appears that NSTreeController is little help in coordinating my two
views. (By the way, I've always had my add, delete functions work directly
on the model in the past.)
It seems to me now it would be better and simpler to go back to using a
data source approach, and use an architecture more like Buck and Yacktman's
figure 29.4 (page 357) with a handmade mediating controller.
Any suggestions or comment!?
John V
_______________________________________________
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:
This email sent to email@hidden