Re: What's the argument aTableView used for?
Re: What's the argument aTableView used for?
- Subject: Re: What's the argument aTableView used for?
- From: Todd Blanchard <email@hidden>
- Date: Tue, 18 Sep 2007 10:24:48 -0700
Maybe, maybe not.
I have a pair of table views (masquerading as scrolling lists) that
are a sort of master detail view on an NSDictionary with string keys
and array values. Pick a key in one table view and I show the values
and I show the values in a second one.
So, realistically, both tables are using the same data source (the
NSDictionary) but showing different facets of it. So I have one
datasource, two table views, and the datasource does different things
depending on which table view is asking for info.
For this case, this is "The Simplest Thing That Could Possibly
Work"(tm).
On Sep 18, 2007, at 1:54 AM, Frank Bettger wrote:
Thanks, Chris,
I suspected that, but wouldn't it be cleaner if you had multiple
dataSource
objects, one for each NSTableView instance. (Even if there are
interdependencies between the tables there is nothing preventing
you from
reading other table models from within your code.) Is there any
advantage to
use the same object for multiple NSTableView instances?
On 9/18/07, Chris Suter <email@hidden> wrote:
In case you use the same object for multiple NSTableView instances.
_______________________________________________
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
_______________________________________________
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