Yes, and I think there was a mistake in my code. I have it almost working and have to analyse now, why it does not work for all cells, which may again be my mistake. I will investigate and post an update and if I don't find it, I will build a simple test program to illustrate this.
On Wed, Jan 28, 2015 at 5:06 PM, Werner Lehmann < lehm...@media-interactive.de> wrote: > That's strange because then TableView would have to create cells always > new instead of reusing them - if they would be reused you would see the > updateItem calls you are saying do never occur... As far as I know the > number of cells is about as many as you need for one visible page in the > tableview plus 2-4 more to facilitate scrolling. > > > On 28.01.2015 15:47, Robert Krüger wrote: > >> To clarify: I am using the stack approach you describe and I remove it >> from the stack when updateItem for a table cell is called that already >> has a different item set. Then I remove the already set item from the >> stack but that never seems to happen in my example. >> > > -- Robert Krüger Managing Partner Lesspain GmbH & Co. KG www.lesspain-software.com
