Home/ Questions/Q 4027140
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T11:03:34+00:00

I have a UITableView Controller and a UITableView. I have everything set up using

  • 0

I have a UITableView Controller and a UITableView. I have everything set up using the delegates etc, and it populates fine. I notice a small bug however with the following method:

:cellForRowAtIndexPath

I am noticing that this method is continually called every time I scroll the table. Even after the table is populated, it continues to call. Basically, a cell moves out of view, when it comes back in view, it is calling it again. I had NSLog print out the cell contents within that method, which is how I know it continues to call.

Should that function not just call once per cell, to populate it, then be done?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Nope. That’s called every time a cell is needed, and a cell is needed every time one is rendered.

    UITableView is a very clever little critter. It literally keeps only the cells it’s displaying, plus a cache of literally two or three more. When the time comes to scroll a cell on that wasn’t on, it can be asked for a cell from the cache, and if there is one, it gets reused.

    This way HUGE data sets can be displayed in a UITableView, because there really aren’t a large number of cells in memory, only the ones on the screen and a small cache.

    • 0