> This suggests to me that ABRecord (the superclass of ABPerson, the > documentation says) may override valueForKey: with new behavior that doesn't > call custom accessors or return anything useful. If that's so, I can only > speculate that it's to prevent you using valueForKey when you're "supposed" > to use valueForProperty instead. > > Does that sound plausible?
Quite plausible. That only strengthens my assertion that using your own home-grown object will work around this problem. If this is indeed the case (-valueForKey:... being overridden to do strange things), probably the easiest design for your new Person object would be to simply have a single iVar (the person's record ID), then add accessors for the fields you're interested in. Your accessors would then access the AB record using the ID stored in your iVar and provide the right answer. -- I.S. _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
