Core Data model with two entities: A and B.

A has property aValue and a relation theBs to one or more Bs.

B has a property bValue.

Two NSTableViews (tabelView1 and tableView2 ) with each controlled by an 
NSArrayController (arrayController1 and arrayController2).

Everything works fine when I send:
 [ arrayController1 setFilterPredicate: "aValue BEGINSWITH[n] "a""];
 [ arrayController2 setFilterPredicate: "aValue containsInside: "a""];
(Well, I do send real predicates, but they contain the strings shown above. 
"containsInside:" is declared in a category on NSString)

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

When later I reset the filterPredicates back to the simple (working) mode, I 
get another exception:
 HIToolbox: ignoring exception 'Cannot remove an observer <arrayController1> 
for the key path "theBs.bValue" from <A-entity 0x114f02a10> because it is not 
registered as an observer.' that raised inside Carbon event dispatch

1. This is a Cocoa document based app, using Core Data. Why this "Carbon event 
dispatch". And who is HIToolbox?

2. I have an identical app, which works perfectly.
(Obviously these two apps are NOT identical, but I really cannot find any 
differences. I tried to remove all changes I made to the newer app, but the 
exception remains).

I spend now more than a day chasing this exception. Any hints would be most 
welcome. 10.6.2.


Kind regards,

Gerriet.

_______________________________________________

Cocoa-dev mailing list ([email protected])

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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to