Comments on: UITableView and Memory

By: Nick

Nick — Thu, 06 May 2010 22:04:07 +0000

@Patty: Your table view needs to be backed by a data model that is separate from the cells. As each cell needs to be rendered (in cellForRowAtIndexPath) you get the data to populate the cell. (This is the Model in the Model-View-Controller pattern.)

By: Patty

Patty — Sun, 02 May 2010 14:27:05 +0000

What if I want to make a table for use as a “configuration page”?
(Like “settings”.)
Each cell having a various object (switches, sliders, textfields, etc).

I have 12 rows… and don’t really need to “create more” or “reuse” anything.

How would that be done?

(My current code works… except when I scroll… then my objects “forget” their settings.)

By: Nick

Nick — Fri, 30 Apr 2010 06:23:16 +0000

@Cory: First I want to caution against relying on an assumption that there will only ever be ~10 items in a list, unless it's based on something that is very unlikely to change, like the months of the year. Software requirements have a strange way of morphing in unexpected ways over time. I don't have any code to post for the general case with larger lists with images. But markj has a good post with lots of improvements in the comments. There's also sample code from Apple that deals with this issue.

By: Cory

Cory — Wed, 28 Apr 2010 09:52:59 +0000

“Yes, it’s much easier to deal with asynchronous download of images for each row if you know how to uniquely identify the cell”

Do you have a good strategy for dealing with this?
I’m only breaking the cell reuse code of conduct in one place in the app I’m currently working on. I think I’m ok, because there really really really will only ever be ~10 items in that table view. But I would be very interested how -you- would deal with async image downloads in a table view.

Good post!