On 7/19/12 2:15 AM, Quincey Morris wrote:
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.)
That doesn't sound right. The array controller is used by views directly, they
bind to arrangedObjects (like in the example). Since when is it recommended to
insert an intermediate object between table view and NSArrayController? Makes
the whole binding idea rather useless, or am I missing something?
Regards
Markus
--
__________________________________________
Markus Spoettl
_______________________________________________
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
