On Mar 25, 2014, at 21:11 , Quincey Morris <quinceymor...@rivergatesoftware.com> wrote:
> On Mar 25, 2014, at 19:57 , Rick Mann <rm...@latencyzero.com> wrote: > >> The problem is that I have to specify an NSManagedObject subclass in IB for >> the NSArrayController, so it seem that I have to make a more general base >> class in Core Data for the objects that are selectable, is that right? > > Have to specify? I don’t recall the Core Data variant of NSArrayController’s > IB interface specifically, but you should only need to specify a class there > (or, rather, it only matters what class you specify there) if you’re using > the array controller to create new objects for you. In that case, it needs to > know what class of objects to create. Otherwise, the class should be > irrelevant. All that matters is that the objects at the other end of bindings > through the array controller respond to the key paths you’re using in the > binding. Hmm. I think it only started complaining when I checked "Prepares Content," but it didn't seem to work at all until I did that. If I add new objects to Core Data, must it be done via the controller, or will it pick all the new ones up in the NSManagedObjectContext? -- Rick
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
