Okay, I am having another UITableView problem. For some reason the indexPath.row is all jumbled up. When I comment out the if statement that sets up the cell, everything works fine. The NSLogs tell me that they are loading in order, but all the cells are out of order.
It also seems as if they repeat; I only see 8 cells, and they repeat over and over.
Here’s my code:
// Customize the appearance of table view cells.
- (UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath {
static NSString *CellIdentifier = @"Cell";
NSLog(@"row: %d",indexPath.row);
UITableViewCell *cell = [tableView dequeueReusableCellWithIdentifier:CellIdentifier];
if (cell == nil) {
cell = [[[UITableViewCell alloc] initWithStyle:UITableViewCellStyleDefault reuseIdentifier:CellIdentifier] autorelease];
cell.selectionStyle = UITableViewCellSelectionStyleNone;
cell.backgroundColor = [UIColor clearColor];
cell.contentView.backgroundColor = [UIColor clearColor];
// Add subviews like this:
// [[cell contentView] addSubview:objectName];
// And I get the row number like this: indexPath.row when getting objects from the array
}
return cell;
}
To use your code:
” I only see 8 cells, and they repeat over and over.” Correct.
What your missing is that that is how it is supposed to work. That’s why only if the cell is nil are you alloc & init’ing a new cell. So you alloc and init and set the colors and add subviews in the if statement. Then after the
if(cell==nil)you know you have a valid cell to populate with some data according to theindexPathvariable passed in.The problem is that now you are setting up the cell when it is nil and assigning all of the displayed data according to the
indexPathpassed in. The problem is cell is not nil the second time it’s used so the data is never changed.To address your speed comment further, I’ll use an old fallback example.
If you look at the sample above, you’ll see that we add a
UILabelto the cell setting it’s tag to 300. Then after the if statement we will have either a brand new cell or a reused cell with text already in the label. No matter either way we simply change the text of the existing label to whatever it should be considering the row. In this way we avoid creating views over and over.If you are dead-set on caching your
UITableViewCellsyou could do so like this:Note When running this on device don’t be surprised when in the console you see
Received memory warningWhat’s efficient & what’s easy are often not the same.