Skip to main content

Delete UITableViewCell and ALL of that cell"s data



I have a UITableViewCell. I can add and subtract 1 from the cell's textLabel and I can also delete the cells. Here is my problem, Lets say i add 5 to the value of the textLabel . And this cell is at the 0 indexPath (The First cell in the table). When I delete this cell and there are now no longer any cells on the table, I add a new cell and this new cell automatically gets the same value as the cell that was just deleted. SO this new cell will have a value of 5 and i want the cell to have a value of 1 just like every cell should when it is added. This only happens when a cell is deleted and a new cell is added at that exact same indexPath. So my question is: do i have to delete this cells "memory" or "data" for this to be fixed? Thanks a bunch for the help!





CellForRowAtIndexPath :







- (UITableViewCell *)tableView:(UITableView *)tableView cellForRowAtIndexPath: (NSIndexPath *)indexPath

{

static NSString *CellIdentifier = @"Cell";



cell = [tableView dequeueReusableCellWithIdentifier:CellIdentifier];

if (cell == nil)

{

cell = [[UITableViewCell alloc] initWithStyle:UITableViewCellStyleDefault reuseIdentifier:CellIdentifier];

addBtn = [[UIButton alloc]init];

addBtn =[UIButton buttonWithType:UIButtonTypeRoundedRect];

[addBtn setFrame:CGRectMake(220,10,25,55)];

[addBtn addTarget:self action:@selector(addLabelText:) forControlEvents:UIControlEventTouchUpInside];

[addBtn setTitle:@"+" forState:UIControlStateNormal];

[addBtn setEnabled:YES];

[cell addSubview:addBtn];



subBtn = [[UIButton alloc]init];

subBtn=[UIButton buttonWithType:UIButtonTypeRoundedRect];

[subBtn setFrame:CGRectMake(260,10,25,55)];

[subBtn addTarget:self action:@selector(subtractLabelText:) forControlEvents:UIControlEventTouchUpInside];

[subBtn setTitle:@"-" forState:UIControlStateNormal];

[subBtn setEnabled:YES];

[cell addSubview:subBtn];



//cell.textLabel.text = @"1";





}

//cellText.hidden=!self.editing;

[cell setSelectionStyle:UITableViewCellSelectionStyleNone];

cell.imageView.image = [imageArray objectAtIndex:indexPath.row];

cell.textLabel.text = [number objectAtIndex:indexPath.row];





return cell;

}




Comments

  1. When cells are deleted or go off screen, the table view saves them and reuses them later. So you need to reset textLabel's value in tableView:cellForRowAtIndexPath:. The UITableViewCell class reference says this:


    The table view's delegate in tableView:cellForRowAtIndexPath: should always reset all content when reusing a cell.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex