FROM : mmalc Crawford
DATE : Sun May 18 16:52:04 2008
On May 18, 2008, at 7:44 AM, Christiaan Hofman wrote:
> Unless there is no way to get the design right.
>
If there is no way to achieve what you want directly with KVO/
bindings, then the answer is not to use KVO/bindings, not to advocate
a "solution" that is known to be wrong.
> 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.
>
<http://developer.apple.com/documentation/Cocoa/Conceptual/CoreData/Articles/cdFAQ.html#//apple_ref/doc/uid/TP40001802-SW3
>
mmalc
DATE : Sun May 18 16:52:04 2008
On May 18, 2008, at 7:44 AM, Christiaan Hofman wrote:
> Unless there is no way to get the design right.
>
If there is no way to achieve what you want directly with KVO/
bindings, then the answer is not to use KVO/bindings, not to advocate
a "solution" that is known to be wrong.
> 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.
>
<http://developer.apple.com/documentation/Cocoa/Conceptual/CoreData/Articles/cdFAQ.html#//apple_ref/doc/uid/TP40001802-SW3
>
mmalc






Cocoa mail archive

