On 7/18/12 2:14 AM, Ken Thomases wrote:
I would check if an exception has been thrown during the setting of the filter, thus interrupting it from rearranging the objects. My suspicion is that you have a KVO-compliance bug that means that it can't unregister an observation.
That would log into the console, wouldn't it? I have no exceptions logged, and I have a symbolic exception breakpoint and NSKVODeallocateBreak that would fire as well.
I did overwrite -arrangeObjects: to see if something suspicious happens. With the exception that it starts working with the subclass for no good reason, there are not other oddities I can see.
By the way, I would not expect automaticallyRearrangesObjects == NO to prevent rearranging when a new filter predicate is set. That property is about whether or not the array controller watches the relevant properties of the content objects so that, if they change in a manner which would affect whether they're filtered or how they're sorted, the array controller rearranges them. It doesn't have to do any such elaborate watching to know to rearrange its objects when the filter predicate or sort descriptors themselves change.
Thanks a lot for the explanation. From the documentation on automaticallyRearrangesObjects that's a little difficult to derive.
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
