Re: more on two-way bindings and one-way bindings
Re: more on two-way bindings and one-way bindings
- Subject: Re: more on two-way bindings and one-way bindings
- From: Matt Neuburg <email@hidden>
- Date: Fri, 07 Jul 2006 12:43:01 -0700
- Thread-topic: more on two-way bindings and one-way bindings
On Fri, 07 Jul 2006 12:02:21 -0600, Keary Suska <email@hidden>
said:
>on 7/6/06 2:03 PM, email@hidden purportedly said:
>
>> No, in code, set NSObjectController's content (using setContent:) to
>> @"byebye". Back in MyObject, "thing2" is still @"howdy"! So even this, a
>> binding established in the standard way, in IB, between a controller and a
>> model object, is only one-way!!
>
>I may be wrong, or misunderstanding the issue, and forgive me if I am
>reiterating what you already know, but my understanding is that setContent:
>sets the content *object*, and not the value. I.e., it sets the *model
>object* that the controller will use.
I completely agree. Still, this isn't what I would have expected setContent:
to mean. I would expect setContent: to change the content object *and*, by
the same token, hand that object through the binding. Instead, it apparently
breaks the binding. I don't think the docs quite make that clear (though
they almost do).
I'll probably be more explicit about what I'm trying to do, in a different
note. m.
m.
--
matt neuburg, phd = email@hidden, <http://www.tidbits.com/matt/>
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
<http://www.amazon.com/gp/product/0596102119>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden