On Jan 6, 2009, at 10:44, WT wrote:
It just occurred to me, though, that the KVO mechanism *could* do
something special for dependent keys, namely, pass the original
change dictionary on to the observer of the dependent key. After
all, it does know that it's dealing with a dependent key. As
It just occurred to me, though, that the KVO mechanism *could* do
something special for dependent keys, namely, pass the original change
dictionary on to the observer of the dependent key. After all, it does
know that it's dealing with a dependent key. As it is, once I get the
notification
Hi Quincey,
thank you for your reply.
In this scenario, typically the dependent property doesn't have a
useful value -- all you care about is the notification.
Yes, that's my intention.
If you *are* trying to maintain a genuine value for the
"displayNeeded" property, then we need to see t
On Jan 6, 2009, at 06:55, WT wrote:
The reason for the comparison between the old and new values should
be obvious, namely, I don't want to redraw the screen unless the
value of the original key has in fact changed.
Now, here's the problem: when I run my app, both the old and new
values a
