CellForRowAtIndexPath scrolling issue

[agnos5]

Hi everyone,
I am having problems with a tableView in a project I am working on. The data loads into the table perfectly at first, but when I scroll to see the remaining data, the NSMutableArray that I am using has the correct number of elements, however it is filled with invalid data (its an array of objects).

Heres how I define the array in the view controller's .h file:

NSMutableArray *appts;

and

@property (nonatomic, retain) NSMutableArray *appts;

in viewDidLoad I am populating the array from a method that returns NSMutableArray:

self.appts = [dbTran selectAppointments:[NSDate date]];

In cellForRowAtIndexPath I am getting the data from the array:

Appointments *appt = (Appointments *)[self.appts objectAtIndex:indexPath.row];

If I set a breakpoint on the code in cellForRowAtIndexPath, i can see that the appts array has 9 objects, but the properties are invalid for every object.
What am I doing wrong?

I appreciate the help!

Thanks

[BrianSlick]

Too many variables to answer the question.

In what way is the data invalid? Is the data itself incorrect, or is what you see in the table incorrect?

[agnos5]

Originally Posted by BrianSlick

Too many variables to answer the question.

In what way is the data invalid? Is the data itself incorrect, or is what you see in the table incorrect?

I agree. Too many things can go wrong. I tried to be as generic as I can.

after scrolling up when debugging with a breakpoint set, I can see that the array has the correct number of elements, and they are all Appointments objects, but the object's properties are invalid. not blank, nill or any other real value. Its like the object is there, but its not initialized.

Initially, when the tableView loads, the data shows perfectly, and I am able to push to a detail view as well.

[BrianSlick]

Post your cellForRow code.

[agnos5]

Originally Posted by BrianSlick

Post your cellForRow code.

- (UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath:(NSIndexPath *)indexPath {
    
	static NSString *CellIdentifier = @"Cell";
	
	UITableViewCell *cell = [tableView dequeueReusableCellWithIdentifier:CellIdentifier];
	
	if(cell == nil)
		cell = [self getCellContentView:CellIdentifier];
	
	UILabel *lblTemp1 = (UILabel *)[cell viewWithTag:1];
	UILabel *lblTemp2 = (UILabel *)[cell viewWithTag:2];
	
	Appointments *appt = (Appointments *)[self.appts objectAtIndex:indexPath.row];
	NSDateFormatter *formatter = [[NSDateFormatter alloc] init];

	DBTransaction *dbTran = [DBTransaction alloc];
	[dbTran initWithUserName:@"iphone"];

	Customer *customer = [dbTran getNameById:appt.Id];
	lblTemp1.text = [appt.Id stringByTrimmingCharactersInSet:[NSCharacterSet whitespaceAndNewlineCharacterSet]];
	lblTemp2.text = customer.name;
	
	cell.accessoryType = UITableViewCellAccessoryDetailDisclosureButton;

	return cell;
}

[BrianSlick]

If the initial display is correct, that suggests the issue is with getCellContentView.

However, add some log messages to make sure that each of your various data elements is correct before assigning them to the labels.

[agnos5]

Originally Posted by BrianSlick

If the initial display is correct, that suggests the issue is with getCellContentView.

However, add some log messages to make sure that each of your various data elements is correct before assigning them to the labels.

getCellContentView is not the problem, i am simply adding labels to the contentView of the cells to display the data. I can post that if you like, but theres nothing else involved.


Any other thoughts?

Thanks

[BrianSlick]

Well, you either have a data problem or a display problem.

If it is a data problem, log messages should help to reveal that. Add them and see what they say.

If it is a display problem, the only atypical thing I see here is getCellContentView. I'd be curious to see what you're doing there, since the name sounds awkward. Cell vs. content view is an important distinction.