Re: KVC Problems with Indexed Accessor for To-Many Properties
Re: KVC Problems with Indexed Accessor for To-Many Properties
- Subject: Re: KVC Problems with Indexed Accessor for To-Many Properties
- From: joe OneNinetyTwo <email@hidden>
- Date: Fri, 13 Oct 2006 19:13:49 -0700 (PDT)
Scott,
I agree that bindings would be better.
However, I need to avoid an array of objects, because
my array of data points will likely contain millions
of points. That's why I am packing them into an
NSData object, and thought I could write indexed
accessor methods to use with an NSArrayController.
If the table was read-only I would have been fine.
Not sure what you mean by creating a simple class with
a dictionary inside. Why would that give me more
flexibility over an NSMutableDictionary? Seems like
I would still need the arrayController to notifiy me
with a modified object (table row), so I could update
my NSData object correspondingly. - Philip
--- Scott Stevenson <email@hidden> wrote:
>
> On Oct 13, 2006, at 6:28 PM, joe OneNinetyTwo wrote:
>
> > I don't really see how I can do what I want using
> an
> > NSArrayController. It looks like I'll have to
> > implement a data source for the NSTableView.
>
> I found that usually when people say that they're
> wrong. :)
>
> It might be easier overall to just create a simple
> class which has a
> dictionary inside. Bindings is a lot more valuable
> than it looks on
> the surface. Don't give it up easily.
>
> - Scott
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden