Re: Problems with bindings and "continuously updates"
Re: Problems with bindings and "continuously updates"
- Subject: Re: Problems with bindings and "continuously updates"
- From: Paul Bruneau <email@hidden>
- Date: Fri, 19 Oct 2007 08:39:14 -0400
On Oct 18, 2007, at 11:02 AM, Fritz Anderson wrote:
On 18 Oct 2007, at 9:52 AM, Timothy Collett wrote:
I'm having some troubles with some read-only bindings. I have
several NSString values that are composites of other values (so
there's no setMyStringValue method, just a myStringValue method),
and they are not being checked properly by the text fields that
are bound to them, even when I have "Continuously Updates Value"
checked.
Have you called setKeys:triggerChangeNotificationsForDependentKey:
in your model's +initialize method, so changing the components of
your composite values will signal a change in your composites?
I have a possibly similar situation so I am looking with interest at
this thread.
Your suggestion seems very good if he had an instance variable for
the composite value, but as he said, he has no -setMyStringValue
method--his composite is generated on the fly with only -
myStringValue. So is
setKeys:triggerChangeNotificationsForDependentKey still relevant?
_______________________________________________
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