Thanks for the responses. I had used KVO on the bound property on an
earlier version and was encountering a small problem due to the nature
of my application. There might be cleaner way so some more details
might be helpful.
I'm writing an application that connects to my home theater receiver
on i
On Apr 15, 2009, at 12:04, Jeff Hutchison wrote:
I am relying on the binding messages to complete before the
target-action message - is this an OK idea?
If you look at the diagram in:
http://developer.apple.com/documentation/Cocoa/Conceptual/CocoaBindings/Concepts/MessageFlow.html#/
/apple_
> I am relying on the binding messages to complete before the
> target-action message - is this an OK idea?
It sounds like you already know the answer to that. It's likely not
worth the trouble of trying to straighten out the race condition, when
you can just dodge the problem entirely and use KVO
On Wed, Apr 15, 2009 at 3:04 PM, Jeff Hutchison
wrote:
> I am relying on the binding messages to complete before the
> target-action message - is this an OK idea?
Why not just register as an observer of the bound property?
--Kyle Sluder
___
Cocoa-dev
I've pored over the documentation pretty thoroughly but haven't found
anything applicable to my situation. I am combining the use of
bindings and target-action. My testing shows it works, but I wanted a
sanity check.
Example of what I am doing:
1. A NSTextField is bound to property "foo" of model
