FROM : mmalc Crawford
DATE : Sun May 18 08:18:00 2008
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.
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
DATE : Sun May 18 08:18:00 2008
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.
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






Cocoa mail archive

