Re: My bindings-enabled NIB ate itself... ?
Re: My bindings-enabled NIB ate itself... ?
- Subject: Re: My bindings-enabled NIB ate itself... ?
- From: Steven Palm <email@hidden>
- Date: Sun, 28 Nov 2004 21:31:22 -0600
On Nov 28, 2004, at 9:23 PM, mmalcolm crawford wrote:
On Nov 28, 2004, at 6:12 PM, Steven Palm wrote:
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.
Are you establishing any bindings programatically? Did you remove all
other bindings? What happens if you start with a completely new nib?
No programatic bindings, all through IB. I'm not sure what you mean
about removing all other bindings... And starting with a new NIB, are
you serious? :-) I've got a lot of bindings established in there, and
I don't know of any good way to get a dump of those to recreate them
without going through the whole process again of figuring out what I
want where.
Perhaps this is a HUGE downside of using Cocoa Bindings...
There is no way to diagnose this without trashing it all and starting
over?
By the way, after a bit more tinkering the error has changed slightly:
2004-11-28 21:25:00.780 myProg[1478] [<NSCFArray 0x37eee0>
addObserver:forKeyPath:options:context:] is not supported. Key path:
configs
2004-11-28 21:25:00.781 myProg[1478] *** Uncaught exception:
<NSInvalidArgumentException> [<NSCFArray 0x37eee0>
addObserver:forKeyPath:options:context:] is not supported. Key path:
configs
Now it's NSCFArray instead of NSAutoreleasePool. Although it must be
said that between the time things were working right and when they went
awry, I hadn't changed anything in the NIB file.
Even doing a debug isn't of much help... Although here is the
backtrace:
#0 0x90a5c638 in -[NSException raise]
#1 0x90a5c624 in +[NSException raise:format:]
#2 0x931aed84 in -[_NSModelObservingTracker
_registerOrUnregister:observerNotificationsForKeyPath:]
#3 0x931afd94 in -[_NSModelObservingTracker
analyzeKeyPath:registerOrUnregister:]
#4 0x931d8884 in -[NSController addObserver:forKeyPath:options:context:]
#5 0x931b85bc in -[NSBinder _updateObservingRegistration:]
#6 0x931b9708 in -[NSBinder establishConnection]
#7 0x931b1498 in -[NSObject(NSKeyValueBindingCreation)
bind:toObject:withKeyPath:options:]
#8 0x92df1b90 in -[NSIBObjectData
nibInstantiateWithOwner:topLevelObjects:]
#9 0x92ee354c in +[NSCustomResource pushBundleForImageSearch:]
#10 0x92e3a798 in +[NSBundle(NSNibLoading)
_loadNibFile:nameTable:withZone:ownerBundle:]
#11 0x92eb95c8 in +[NSBundle(NSNibLoading)
loadNibFile:externalNameTable:withZone:]
#12 0x92ecadbc in +[NSBundle(NSNibLoading) loadNibNamed:owner:]
#13 0x92eb9430 in NSApplicationMain
#14 0x00007c90 in _start at crt.c:267
#15 0x8fe1a558 in __dyld__dyld_start
However, that doesn't seem to say much about which binding it's having
problems with.
Thanks,
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