> Define "doesn't work" - if you mean observeValue:forKeyPath:... doesn't get
> called,
Indeed that's what I meant.
> it's because that's a different relationship from bindings.
Just assumptions (I know) but I would think the default implementation
does something similar to the code shown in th
On Sep 20, 2011, at 02:13 , Torsten Curdt wrote:
> Before I was following the docs and wrote the bindings clue code myself
>
> http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/CocoaBindings/Concepts/HowDoBindingsWork.html#//apple_ref/doc/uid/20002373
>
>- (void)bind:(NS
Define "doesn't work" - if you mean observeValue:forKeyPath:... doesn't get
called, it's because that's a different relationship from bindings. With
bindings, a change in one value causes a change in another. With observers, a
change in one value causes a call to the observeValue method.
On S
On Apr 28, 2009, at 06:04, Simon Raisin wrote:
I'm running into a binding issue is my main application so I wrote a
small
test app to try to track down the problem: primarily that I cannot
get the
UI to update appropriately when it is configured to observe my model
objects
via bindings.
.
