Re: Cocoa Custom NSCell Binding Issue
Re: Cocoa Custom NSCell Binding Issue
- Subject: Re: Cocoa Custom NSCell Binding Issue
- From: Hamish Allan <email@hidden>
- Date: Fri, 13 Jan 2006 00:39:20 +0000
On Thu, 12 Jan 2006 09:35:13 -0600, Sean Willson
<email@hidden> wrote:
On 1/12/06, Hamish Allan <email@hidden> wrote:
It sounds like your setObjectValue: method is being called, but is
your objectValue method? Which way round are they being called?
I have fully implemented the objectValue method conforming to the
interface,
added some NSLog statements in there to see if it ever gets called
and it
does not. Is there something special that I have to do to get this
working.
How does the NSArrayController that is controlling the Object A
references
and binding to the UI get notified that the componant has set a new
value
that it needs to propigate down to Object A? That seems to be the
part that
is missing. That's why I said that I tried firing the "will" and "did"
change notifications for objectValue but that didn't work. I know
this has
to be something small but I can't seem to find any examples that
show a
custom NSCell type element using Cocoa Bindings.
If you're handling change notifications manually ("will" and "did"),
your object must implement +automaticallyNotifiesObserversForKey:
appropriately (see http://developer.apple.com/documentation/Cocoa/
Conceptual/KeyValueObserving/Concepts/AutoVsManual.html). It may be
easier just to write your setObjectValue: in such a way that it can
be called in response to a user clicking in the custom NSCell.
Hamish
_______________________________________________
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