title: TableView Cell reuse and unwanted checkmarks - this is killing me
body: <p><br> Apple's iOS <code>TableView</code> and cell reuse is killing me. I searched and searched and studied, but can't find good docs or good answers. The problem is that when the <code>TableView</code> reuses cells things like Checkmarks (cell accessory) set on a selected Cell are repeated in the cells further down in the table view. I understand that cell reuse is by design, due to memory constraints, but if you have a list with say 50 items, and it starts setting extra checkmarks where they're not wanted, this makes whole endeavor useless.</p>
  
  <p>All I want to do is set a checkmark on a cell I've selected. I've tried this using my own custom cell class, and standard cells generated by a boiler plate TableView class, but it always ends up the same.</p>
  
  <p>Apple even have an example project called TouchCell you can download from the dev center, that is supposed to show a different way of setting a checkmark using a custom cell with an image control on the left. The project uses a dictionary object for a data source instead of a muteable array, so for each item there is a string value and bool checked value. This bool checked value is supposed to set the checkmark so it can track selected items. This sample project also displays this goofy behavior as soon as you populate the TableView with 15+ cells. The reuse of cells starts setting unwanted check marks. </p>
  
  <p>I've even tried experimenting with using a truely unique Cell Identifier for each cell. So instead of each cell having something like @"Acell" I used a static int, cast to a string so the cells got @"cell1", @"cell2" etc. During testing though, I could see that hundreds of new cells where generated during scrolling, even if the table only had 30 items. </p>
  
  <p>It did fix the checkmark repeat problem, but I suspect the memory usage was going way too high.</p>
  
  <p>It's as though the cells that are not currently in the viewable area of the table are created all over again when they are scrolled back into view. </p>
  
  <p>Has anyone come up with an elegant solution to this irritating behavior?</p>