NSManagedObjectContext - Key Value compliant
NSManagedObjectContext - Key Value compliant
- Subject: NSManagedObjectContext - Key Value compliant
- From: Keith Wilson <email@hidden>
- Date: Sun, 28 Oct 2007 18:04:30 +1100
Using Xcode 2.4 Tiger 10.4.10 I had a subclass of an
NSManagedObjectContext and used setValue and valueForKey on the extra
ivars I had defined. Worked fine on Tiger PPC and Intel. The compiled
app failed to launch in Leopard.
I have imported the project into XCode 3.0, Intel Leopard 10.0. I
have so far found that most (probably every) setValue:ForKey and
valueForKey on any of the iVars for the subclassed Moc fails. No
message, no warning, not even when using the debugger, silence - and
not going nowhere fast.
Is this a bug or has there been a design change that I have missed.
I can get-around it by adding glue code for each get and each set in
the Moc subclass
Can someone tell me which other Object Classes will exhibit this odd
behaviour in Leopard.
Keith
_______________________________________________
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