Re: Controller Selection Synchronization
Re: Controller Selection Synchronization
- Subject: Re: Controller Selection Synchronization
- From: Quincey Morris <email@hidden>
- Date: Sat, 09 Apr 2011 21:12:50 -0700
On Apr 9, 2011, at 18:00, Richard Somers wrote:
> I have a primary view which displays all objects using a primary controller. Both 'A' and 'B' objects are included in the controller content. This is accomplished by using an abstract class in the managed object model that is a parent of both 'A' and 'B' objects. The primary array controller content is the abstract class, so we get all objects.
Are you talking about selecting rows in a table view or an outline view, or selecting objects in a custom view?
If you're talking about a table/outline view, I'd just use the "selection did change" delegate methods to propagate selections from one list to another.
If not, but the selection is part of the state of a window controller, I'd make a window controller property for each list, and observe those properties, either in the window controller or the individual views.
Or, if the selection is to be saved with the data model, I'd put a (probably just one) selection set property in the data model, and use the window controller (for example) as a mediating controller to propagate derived properties to the views.
_______________________________________________
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