Re: Cocoa-dev Digest, Vol 4, Issue 1015
Re: Cocoa-dev Digest, Vol 4, Issue 1015
- Subject: Re: Cocoa-dev Digest, Vol 4, Issue 1015
- From: Ron Lue-Sang <email@hidden>
- Date: Mon, 15 Oct 2007 12:11:08 -0700
On Oct 15, 2007, at 12:03 PM, email@hidden wrote:
Date: Mon, 15 Oct 2007 11:17:19 -0700
From: Steve Checkoway <email@hidden>
Subject: Re: Binding NSPopupButton crashes
To: "I. Savant" <email@hidden>
Cc: cocoadev Mail <email@hidden>
Message-ID: <email@hidden>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I. Savant wrote:
I am trying to bind an NSPopupButton to the user defaults in
Interface
Builder as well as programatically binding a property in another
class
to the same user default value. The NSPopupButton is in the
preferences window for the application.
You're going to have to be *way* more specific. What properties of
the button are you binding? To what controller and key? What code are
you using when establishing the binding programatically? What does
the
stack trace look like? Are you really trying to establish the same
binding both with Interface Builder and programmatically (or have I
simply misunderstood)? If so, why do you feel that's necessary?
I've noticed that too specific gets no responses on this list. See my
previous unanswered query, for an example. =) That said, here's some
more information.
The part of my text you quoted says that I'm binding a property in
another class to the user default value, so no, I'm not doing the same
binding in both IB and programatically.
In IB, I'm binding the selected value of the popup button to the
shared
user defaults controller with the key path "values.foo".
Programatically, I have the following.
NSUserDefaultsController *defaultsController =
[NSUserDefaultsController
sharedUserDefaultsController];
[object bind:@"foo"
toObject:defaultsController
withKeyPath:@"values.foo"
options:nil];
I'm afraid I can't give you the stack trace right now because that
computer is sleeping and I don't have the time to recreate it this
moment, but if you really think it'd be useful, I can do it when I go
home in the evening.
--
Steve Checkoway
Your extended description here helps. But the stacktrace or at least
the specific exception and exception message would be needed to
remotely diagnose the problem.
_______________________________________________
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