I would like to have scaler accesors and also standard (NSNumber) accessors in my managed objects. The docs show some ways to handle the former, e.g., "CGFloat myValue". I prefer not to cache. (I'm trying to retrofit an app to CoreData and prefer not to change all my code accesses to deal with NSNumber.)
Assuming I do the above, but occasionally need the NSNumber, is there any reason why I cannot simply add a property, say "NSNumber myValuePrim" (not an attribute or cached value), and implement my own accessors for it, using the primitive value and the proper KVO? I wish CoreData had ways to automatically handle this. _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
