Re: Forcing a refresh on a bound control

FROM : Christiaan Hofman
DATE : Sun May 18 12:20:00 2008

On 18 May 2008, at 8:18 AM, mmalc Crawford wrote:

>
> On May 15, 2008, at 2:35 PM, Christiaan Hofman wrote:
>

>> You can force a KVO notification by sending a will/
>> didChangeValueForKey:
>> pair of messages.
>>

> As has been said on numerous occasions, no, don't do this.
>


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.

Christiaan

>
> On May 15, 2008, at 2:10 PM, Trent Jacobs wrote:
>

>> In my core data app I have an entity which I chose to derive from a 
>> NSManagedObject class because I wanted to do some formatting and 
>> data manipulation on one of the attributes which I have bound to a 
>> NSTextView. The formatting is conditional based on a chechbox on 
>> the UI (in the preferences panel).
>>

> It's not clear why the formatting should be part of the behaviour of 
> the managed object class.  It would seem more appropriate to move 
> the formatting logic to another object which then either has a 
> reference to the checkbox or observes a value that the checkbox 
> modifies.
>
> mmalc
>
> _______________________________________________
> MacOSX-dev mailing list
> <email_removed>
> http://www.omnigroup.com/mailman/listinfo/macosx-dev