On Jul 18, 2012, at 08:52 , Markus Spoettl wrote: > I also looked at the predicate operator type as a potential source of the > issue but I can't see a problem there. I'm using > NSEqualToPredicateOperatorType is fine, as I do want a comparison using > -equalTo: . NSMatchesPredicateOperatorType produces the correct result
Oddly, the other operators (e.g. NSGreaterThanOrEqualToPredicateOperatorType) work fine. You might find a workaround using a combination of predicates using different operators. > I'd be delighted if someone told me it's all my fault. Can anyone point out > the error? Maybe you're a *bit* at fault by designing your app around the assumption that there's a single, coalesced KVO notification for any change to the array controller. There's really no API contract to that effect. You'd be better off implementing something to prevent the expensive code from running too often. (Then you'd be able to work around the apparent array controller bug by calling 'rearrangeObjects' manually.) _______________________________________________ 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
