Question

I have a pretty standard setup where I have an array in my controller that I’m binding to an NSTableView. When I add an object to this array with the UI, I add elements by copying the array to a mutable array, adding the contents, then copying it back. I saw this idiom somewhere, but I’m not really sure where, or whether this is actually a sane thing to do. I t works fine on Snow Leopard, but it crashes really badly on Leopard. GDB tells me it happens right at the marked line, where I copy the new array back.

@interface MyAppDelegate : NSObject {

    NSArray * urls;
    //other declarations
}
@property (nonatomic, retain) NSArray *urls;


@implementation MyAppDelegate 

@synthesize urls;

- (void)addThing:(id)sender {

    NSMutableArray *newUrls = [NSMutableArray arrayWithArray: [self urls]];

    [newUrls addObject: newurlimadding];
    [self setUrls: [NSArray arrayWithArray: newUrl]]; 
}

I’m pretty sure I must be doing something boneheaded here. Is there a better way to do this? Why am I crashing?

Answer 1

NSMutableArray *newUrls = [NSMutableArray arrayWithArray: [self urls]];
[newUrls addObject: newurlimadding];
[self setUrls: [NSArray arrayWithArray: newUrl]];

What did you create newUrls for if not to set it as the new value of urls?

Besides that, there are a couple of things you’re doing wrong:

1. No model objects. Bindings hates this. Unless your table view exists solely to display the different parts of the URL (scheme, host, path, etc.), each in one column, you’re not giving Bindings what it wants.

   Pay attention to the fields in the Bindings Inspector. Note that there are two: Controller Key and Model Key Path. They’re exactly what they say on their tins: The Controller Key is the key for a property of the controller, which should provide model objects. The Model Key Path is the key path for one or more properties in the model, which usually should provide value objects, such as strings and numbers.

   You probably need to create a model class and make the URL a property of that class. I’d guess that you have other objects, perhaps in parallel arrays, that you can move to properties of the model class. Do that, so that you’re working with Bindings instead of against it.

2. Not using array accessors. You’re just setting the whole array at once, which is inefficient and may cause display problems (such as selection highlights disappearing). Implement and use array accessors for this array property. Accessorizer can help you here.

I actually have no idea whether this will fix your crash because you haven’t told us anything about it. You should edit your question to include any exception messages or other crash-describing output, which you’ll find in the Run Log/Debugger Console.

Also, since the type of urls can be mutable, you should set it to copy, not retain.