Re: Forcing a refresh on a bound control

FROM : Christiaan Hofman
DATE : Sun May 18 16:44:48 2008

On 18 May 2008, at 4:25 PM, mmalc Crawford wrote:

>
> On May 18, 2008, at 3:20 AM, Christiaan Hofman wrote:
>

>> I know it has been said. But I have never heard an alternative to 
>> forcing a KVO change notification. Given that dependent keys can 
>> only be set for the same object... And if you would think there may 
>> be an alternative in this particular situation (though I don't see 
>> it), I am talking about the general situation. Please proof me 
>> wrong, but I couldn't find it.
>>

> This is simply asinine.
> There's nothing to prove wrong.  As Clark suggested, the solution is 
> to get the design right.
>
> mmalc
>


Unless there is no way to get the design right. Perhaps in this 
particular case there is, but in some cases there isn't. In some cases 
there isn't. Two cases I know of are when you have dependent keys in 
different objects in a Tiger compatible app, and dependent keys where 
no KVO notification is send, only an NSNotification. In my apps I have 
both situations. If you can give a way to avoid this, I would be happy 
to hear it, but I don't know of one.

Christiaan