Re: Core Data _NSFaultingMutableSet Exception
Re: Core Data _NSFaultingMutableSet Exception
- Subject: Re: Core Data _NSFaultingMutableSet Exception
- From: Kyle Sluder <email@hidden>
- Date: Tue, 22 Dec 2009 14:01:26 -0500
Do you have an old, unfixed version of your nib in version control
somewhere? (The answer should be "yes;" if not, you might want to
reconsider your approach to version control for the sake of your own
sanity.)
If so, do the same thing you did, confirm that it causes the same
problem, and send the old and new versions of the nib off to Apple in
a bug. There have been instances of this before, where objects simply
weren't written to anticipate a property changing more than once in
the lifespan of that object. These cases are definitely bugs.
--Kyle Sluder
On Dec 22, 2009, at 7:56 AM, "Gerriet M. Denkmann"
<email@hidden> wrote:
On 22 Dec 2009, at 16:20, Jerry Krinock <email@hidden> wrote:
On 2009 Dec 21, at 21:05, Gerriet M. Denkmann wrote:
But when I use:
[ arrayController1 setFilterPredicate: "aValue BEGINSWITH[n] "a"
AND ANY theBs.bValue == "xx""];
I get an exeption:
HIToolbox: ignoring exception '[<_NSFaultingMutableSet
0x1001f5d00> addObserver:forKeyPath:options:context:] is not
supported. Key path: bValue' that raised inside Carbon event
dispatch
I believe I've seen this message when I try to observe the "many"
end of a to-many relation using KVO. That's against the law. (And
I do remember reading that one in the documentation, mmalc!)
Probably it was in the KVO Programming guide??
Bindings uses KVO. Clue: Look at any bindings hanging on that
array controller.
Well, this was an idea I had already. Because the old (working) app
did just have an array controller, but the new app (the one throwing
exceptions) had another array controller bound to the selection of
the first one.
So I did [ secondArrayController unbind: @"contentSet" ] - but no
success.
Then I removed the secondArrayController from the nib - no success
either.
Now, after reading your mail, I deleted the first array controller,
dragged a new one into the nib - and everything works!
Obviously the old firstArrayController had some memory of having its
content bound to by some other controller; a memory persisting
regardless of this binding having been unbound, or the binder having
disappeared.
I am not qualified to call this a bug. But it has cost me more than
a day of pointless struggle.
Is this persistent memory of NSArrayControllers somewhere documented?
And is there a way (programmatically) to clear this unwanted memory?
Thanks for your help!
Kind regards,
Gerriet.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden