My bindings-enabled NIB ate itself... ?
My bindings-enabled NIB ate itself... ?
- Subject: My bindings-enabled NIB ate itself... ?
- From: Steven Palm <email@hidden>
- Date: Sun, 28 Nov 2004 20:12:21 -0600
I'm very confused. This is my first project to attempt to use Cocoa
bindings, and everything was going very well. I was just about to add
in a call to do some KVO to track changes of a particular object, and
when I tried to test it I got a very strange error. I backed out my
most recent changes and the app still is in critical condition... I get
this now:
2004-11-28 20:07:42.964 myProg[1091] [<NSAutoreleasePool 0xa0a04e18>
valueForUndefinedKey:]: this class is not key value coding-compliant
for the key configs.
2004-11-28 20:07:42.971 myProg[1091] *** Uncaught exception:
<NSUnknownKeyException> [<NSAutoreleasePool 0xa0a04e18>
valueForUndefinedKey:]: this class is not key value coding-compliant
for the key configs.
I *really* don't understand where the NSAutoreleasePool reference is
even coming from... 'configs' is part of another class instantiated in
the nib. I tried to remove the instance of the class in Interface
Builder and re-instantiating it, rebuilding the connections/bindings,
and I still get the same error.
How can something like this be traced to find out what went wrong?
Thanks for any tips,
Steve
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden