On Sep 11, 2012, at 4:28 , Charles Srstka wrote:
> On Sep 10, 2012, at 9:23 PM, Quincey Morris
> wrote:
>
>> It doesn't need "all the extra scaffolding". KVC will peer quite happily
>> into your instance variables by default. What you don't get for free, in
>> that case, is KVO compliance
On Sep 10, 2012, at 19:29 , Rick Mann wrote:
> The docs say this is all for KVC compliance. But because the calls are almost
> one-to-one when backed by a simple collection, I'm surprised they don't do it
> for me.
>
> In other words, I could write code to dynamically implement
> -insert:atIn
On Sep 10, 2012, at 19:27 , Charles Srstka wrote:
> On Sep 10, 2012, at 9:23 PM, Quincey Morris
> wrote:
>
>> It doesn't need "all the extra scaffolding". KVC will peer quite happily
>> into your instance variables by default. What you don't get for free, in
>> that case, is KVO compliance
On Sep 10, 2012, at 19:23 , Quincey Morris
wrote:
> On Sep 10, 2012, at 18:48 , Rick Mann wrote:
>
>> The docs say you can implement either insertObject: or insert. I
>> figured it was smart enough to handle the plural-vs-singular change,
>> otherwise it's grammatically awkward.
>
> Well,
On Sep 10, 2012, at 9:23 PM, Quincey Morris
wrote:
> It doesn't need "all the extra scaffolding". KVC will peer quite happily into
> your instance variables by default. What you don't get for free, in that
> case, is KVO compliance for the property. The purpose of providing explicit
> accesso
On Sep 10, 2012, at 18:48 , Rick Mann wrote:
> The docs say you can implement either insertObject: or insert. I figured
> it was smart enough to handle the plural-vs-singular change, otherwise it's
> grammatically awkward.
Well, you were wrong about that. :)
The intention is that to-many prop
On Sep 10, 2012, at 18:39 , Graham Cox wrote:
>
> On 11/09/2012, at 11:29 AM, Rick Mann wrote:
>
>> - (void)
>> insertConnection: (NSDictionary*) inConn
>> atIndex: (NSUInteger) inIndex
>>
>> and the removal counterpart. Didn't help. I recall the mere presence of
>> those in the past f
On 11/09/2012, at 11:29 AM, Rick Mann wrote:
> - (void)
> insertConnection: (NSDictionary*) inConn
> atIndex: (NSUInteger) inIndex
>
> and the removal counterpart. Didn't help. I recall the mere presence of those
> in the past fixed my issues, and I could still add and remove objects to
Despite having successfully written several apps that use bindings, I still
manage to screw it up each time I start a new one.
I have a little object that has an NSMutableArray property called
"connections". I tried to bind an NSArrayController to it, and then bind an
NSTableView to that. But i
