Re: Strange behaviour with NSTableView binded to NSArrayController with NSSet as content
Re: Strange behaviour with NSTableView binded to NSArrayController with NSSet as content
- Subject: Re: Strange behaviour with NSTableView binded to NSArrayController with NSSet as content
- From: Quincey Morris <email@hidden>
- Date: Tue, 3 Nov 2009 10:43:11 -0800
On Nov 3, 2009, at 03:18, Christian Ziegler wrote:
Are you suggesting I should use an NSMutableArray as content instead
of NSMutableSet?
You can't switch. Without a managed object context, a
NSArrayController's content must be provided by a NSArray, and with a
managed object context, a NSArrayController's content must be provided
by a NSSet.
So it sounds like you're using Core Data. Is that correct?
Actually I thought thats what the arrangedObjects array is for. I
only access the model through arrangedObjects. The reason why I use
a Set is just because the objects dont have a natural ordering. The
order in which the tableView presents the objects is just a matter
of the view imo. Funny thing is, even after I added objects, the
arrangedObjects array returns the correct object for each index. Im
doin the moving objects around part myself, so I could debug which
objects I fetch from the array.
Added the objects where? To arrangedObjects? If your underlying data
is unordered, what does "the correct object for each index" mean
(since unordered objects don't have an index)? How are you "moving
objects around"? Sorry, I couldn't follow your explanation when you
started this thread, and I still can't. Maybe it's time for you to
post some code, if you're still looking for an answer.
_______________________________________________
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