Hi, all!  I'm posting this question here because this list keeps coming up
when I search for information on things I'm working on, so I figure if
anyone can figure this out, it'll be here.
I'm trying to add an NSRuleEditor-like interface to my app, but I'm rolling
my own because I gave up on figuring out the official one. :)  It's not that
big a task, anyway, so I'm fine with that...

I have Core Data entities Condition (abstract), CompoundCondition, and
KnowledgeCondition, each with their own custom classes.  Weirdly, I get an
error only when attempting to add a third child to an existing item - I can
delete and add children one and two as much as I want without triggering the
problem, and if I (somehow - I can't reproduce it) get past that, I can
continue to delete and add then as well.  It's only at the transition from
two to three that's the problem.

Anyway, the error looks like:

*2008-04-13 22:27:25.180 Dialogue[56287:10b] *** -[NSCFArray member:]:
unrecognized selector sent to instance 0x10e65f0*

*2008-04-13 22:27:25.181 Dialogue[56287:10b] *** -[NSCFArray member:]:
unrecognized selector sent to instance 0x10e65f0*

Well, yeah - it can't find the selector because it's not a set, it's an
array.  But this is baffling, because I requested it with
mutableSetValueForKey!  Doing po on the address gives me:

<NSCFArray 0x1229830>(

<KnowledgeCondition: 0x126f790> (entity: KnowledgeCondition; id: 0x10ff2a0
<x-coredata:///KnowledgeCondition/t93FFC617-086F-4DFB-9EC8-3A390E2F79A77> ;
data: {

    character = nil;

    index = 0;

    knowledge = nil;

    mode = 1;

    parent = 0x10cf080
<x-coredata:///CompoundCondition/t93FFC617-086F-4DFB-9EC8-3A390E2F79A76>;

    trigger = nil;

}),

<KnowledgeCondition: 0x10dba60> (entity: KnowledgeCondition; id: 0x10df1c0
<x-coredata:///KnowledgeCondition/t93FFC617-086F-4DFB-9EC8-3A390E2F79A78> ;
data: {

    character = nil;

    index = 5;

    knowledge = nil;

    mode = 1;

    parent = 0x10cf080
<x-coredata:///CompoundCondition/t93FFC617-086F-4DFB-9EC8-3A390E2F79A76>;

    trigger = nil;

})

)

Which, indeed, looks like a valid representation of my data - except for
some reason as an array rather than a set.

Does anybody have any idea how I can debug this?

By the way, this problem is similar to one described a couple years ago, but
there was no resolution in that thread.  I'm hoping that means it was
something simple and silly!
http://www.cocoabuilder.com/archive/message/cocoa/2006/1/20/154873

-- 
Dan Knapp
"An infallible method of conciliating a tiger is to allow oneself to be
devoured." (Konrad Adenauer)
_______________________________________________

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

This email sent to [EMAIL PROTECTED]

Reply via email to