> On 11 May 2016, at 07:39, Quincey Morris > <quinceymor...@rivergatesoftware.com> wrote: > > On May 10, 2016, at 16:22 , Carl Hoefs <newsli...@autonomy.caltech.edu> wrote: >> >> I will set 'context' and use it in my check instead. > > Yup, use the context to decide whether to call super *and return* but nothing > else. Once you get past that check, don’t call super. > >> It appears that for some odd reason, once in a blue moon, 'object' and >> 'keyPath' aren't what they're supposed to be, > > It’s not odd, if they’re the object and keyPath of a different observation > registered by a superclass of your class. You’ve proved it happens! > >
Well no he hasn’t - because if it was the object and keyPath of a different observation registered by a superclass of his class then passing it to super would allow that class to handle it, which it would do, and there would not be a crash. So it’s not that. _______________________________________________ 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
