FROM : Hans van der Meer
DATE : Tue Feb 12 23:07:08 2008
On 12 feb 2008, at 22:45, Kyle Sluder wrote:
> On 2/12/08, Hans van der Meer <<email_removed>> wrote:
>> Is there something I do not see? Or do I have to add all the "indexed
>> accessor methods" to NSArray and NSMutableArray in a category?
>> That generates another question: in that case, must I program for
>> manual observing by bracketing the implementation statements with
>> [self willChangeValueForKey ..etc] messages?
>
> You seem to be confused... why would you be listening for changes to
> custom properties on the array itself?
>
I guess so. My intention is to have the NSArrayController following
the changes in the mutable array in order to show these changes in a
tableview in the GUI. As I understand it, to accomplish this the
NSArrayController should observe the changes in the array. Doing
simply [array addObject:] apparently does not trigger the
NSArrayController into having the tableview follow the change.
Hans van der Meer
DATE : Tue Feb 12 23:07:08 2008
On 12 feb 2008, at 22:45, Kyle Sluder wrote:
> On 2/12/08, Hans van der Meer <<email_removed>> wrote:
>> Is there something I do not see? Or do I have to add all the "indexed
>> accessor methods" to NSArray and NSMutableArray in a category?
>> That generates another question: in that case, must I program for
>> manual observing by bracketing the implementation statements with
>> [self willChangeValueForKey ..etc] messages?
>
> You seem to be confused... why would you be listening for changes to
> custom properties on the array itself?
>
I guess so. My intention is to have the NSArrayController following
the changes in the mutable array in order to show these changes in a
tableview in the GUI. As I understand it, to accomplish this the
NSArrayController should observe the changes in the array. Doing
simply [array addObject:] apparently does not trigger the
NSArrayController into having the tableview follow the change.
Hans van der Meer






Cocoa mail archive

