This is a very newbie question, and this is something I have done many times before, but there\'s something I\'m missing this time.
In my AppDelegate.h file I declar
You don't need a data source if you're using Bindings. One or the other.
I have an array controller thats bound to "AppDelegate.self.lines" …
Why self
?
@property(readwrite, retain) NSArray *lines;
No, use copy
here. Otherwise, you'll find yourself retaining someone else's mutable array, which they will then mutate. Then “your” array will have changed without you knowing it.
Then I have a method that sets the lines array:
lines = [fileContents componentsSeparatedByString:@"\n"];
This is why the table doesn't show anything. You're not going through the property, you're accessing the instance variable directly. Direct instance variable accesses do not cause KVO notifications, so the array controller never finds out about the change.
Even worse, you're leaking the old array (since you simply assign over it without releasing it) and under-retaining this new array. Because you're not retaining the new array, that instance variable will hold a dead object shortly. The automatic retaining is done by the setLines:
method, which only gets called when you call it.
You need to go through the property:
self.lines = [fileContents componentsSeparatedByString:@"\n"];
A property access is an implicit accessor message, so this both retains the array (or copies it, once you correct the @property
as I suggested above) and posts KVO notifications.
You might want to read through this, it's got some good diagrams and explanations. What ennuikiller is saying is correct, I think it's a problem with your datasource. This is done by calling
[aTable setDelegate:aDelegate];
When you say you have a arrangedObjects bound to the column do you mean you set the tablview datasource? If not you to set the tableview datasource to the lines array