Re: Problems with bindings and "continuously updates"
Re: Problems with bindings and "continuously updates"
- Subject: Re: Problems with bindings and "continuously updates"
- From: David Spooner <email@hidden>
- Date: Fri, 19 Oct 2007 08:27:05 -0600
On 19-Oct-07, at 6:39 AM, Paul Bruneau wrote:
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?
_______________________________________________
The problem is that the 'value' of the control changes as a result of
key/value observation of myStringValue. The binding option
"Continuously Updates Value" determines how often myStringValue is set
as a result of editing the control (which presumably is never). One
must ensure that key/value observation of myStringValue occurs as a
result of key/value observation of the properties on which it
depends ...
dave
_______________________________________________
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