Re: Cocoa Bindings Question(s)
Re: Cocoa Bindings Question(s)
- Subject: Re: Cocoa Bindings Question(s)
- From: <email@hidden>
- Date: Tue, 20 Jul 2004 9:13:14 -0400
>
no, I checked that too. and the local copy doesn't matter if >it's on or off.
>
>
On Jul 19, 2004, at 5:29 PM, mmalcolm crawford wrote:>
>
> [In the original implementation] Was the array
>
> controller's
>
> "Automatically prepares content" switch set?
>
>
>
> mmalc
Well, mystery solved. The "working" version had a different name for the mutable array, so I changed it, and the accessor functions to match and it was still working. I realized the thing that broke one version was the CASE of the accessor function!
The array was named: booksList
working version: -(void)setbooksList:(NSMutableArray *)newBooksList;
non-working: -(void)setBooksList:(NSMutableArray *)newBooksList;
See the difference? I didn't notice it..
Also, the "working" version (and also the fixed, "non-working" version) do not create the booksList array in the init method ([[NSMutableArray alloc] init]).
Though.. looking at mmalc's "Todo's" sample, his array is named "toDos" and the accessor is "setToDos" and that works... Ok. Got me.... (his version does initialize the array).
So some combination of creating the array makes the case of the accessor not matter?
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.