Thanks for your insight.
The only reason for having access to the model, in my case, is that some of the
properties are derived. (In my case, 4 properties need to be set (by the user)
to derive a final property). But, I do like your approach of simply binding it
all to the same source...was not
On Mar 13, 2012, at 2:28 PM, Michael de Haan wrote:
> What I wish to have happen, is a situation where model and view AND last user
> value saved and restored using the "bindings" model.
> Is this possible?
I'm not really 100% sure what you're after here, so I may be off:
If you literally wante
I am sure this must be covered somewhere, but my searches come to nought.
Using bindings, I wish to persist the state of an app ( for example, a slider's
value).
Current test app is thus.
A slider, whose value is bound to a "model" float value via an appropriate
NSController ( in this case, an
