Re: Almost there with bindings
Re: Almost there with bindings
- Subject: Re: Almost there with bindings
- From: "John C. Welch" <email@hidden>
- Date: Wed, 26 May 2010 22:43:24 -0400
- Delivered-to: email@hidden
- Delivered-to: email@hidden
- Thread-index: Acr9OSWkdY5FsJuKcE6kUaDVz3FT0QABmx+yAAGzkKI=
- Thread-topic: Almost there with bindings
- User-agent: Microsoft-Entourage/12.24.0.100205
On 5/26/10 9:54 PM, "Shane Stanley" <email@hidden> wrote:
> I'm tempted to answer "because that way it works".
Given the arbitrary nature of Xcode, that's not an entirely bad answer.
>
> Bindings rely on key-value observing. In Objective-C, you can change the
> value of a property within a class either directly or via accessor methods;
> both change the value, but only one is key-value observable.
>
> Similarly, in ASObjC, adding the "my" makes the change key-value observable.
> (The change seems to wrap the statement in calls to willChangeValueForKey:
> and didChangeValueForKey: -- how that happens, who knows.)
Ahh...okay. That makes some sense then.
--
Cum catapultae proscriptae erunt tum soli proscript catapultas habebunt.
(When catapults are outlawed, only outlaws will have catapults.)
Jeff La Grua
_______________________________________________
Do not post admin requests to the list. They will be ignored.
applescriptobjc-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden