Core data model persistence, independent of document
Core data model persistence, independent of document
- Subject: Core data model persistence, independent of document
- From: James Maxwell <email@hidden>
- Date: Fri, 21 May 2010 11:30:16 -0700
Looking over the type of model I want to build for my music app, I realized that perhaps Core Data would be a good way to manage it. The reason being that I want an arbitrary number of "Instruments", each of which has a MIDI port, channel, and an arbitrary number of "Articulations." The total set of user-defined Articulations is stored in an "Articulation Library", so that the user can create articulations, and assign them to whatever instruments they desire. Given these relationships, Core Data seemed reasonable...
I built a model that seems about right, to me, but I can't seem to bind it to anything without getting the "this class is not key value coding-compliant for the key managedObjectContext" error. I've been looking around at various Core Data tutorials, and I noticed that they're either for document-based apps, or they're created from a template, which I guess must provide the appropriate AppDelegate (at least, that's implied by one of the tutorials, at mactech.com). My app is document-based, but I don't want this data stored with the document -- it should persist across all documents, pretty much like a user default (and besides, I'm subclassing GCDrawKit's "DKDrawingDocument" already).
I get the same error when binding to Shared User Defaults, so I'm kinda stumped...
thanks,
J.
James B Maxwell
Composer/Doctoral Student
School for the Contemporary Arts (SCA)
School for Interactive Arts + Technology (SIAT)
Simon Fraser University
email@hidden
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