TableView in 2015.2637 reloads below the fold

Hello,

We upgraded from the public release 2014.2511 to today’s 2015.2637 build and yes, there are many things to fix ( good job on all these updates!) but one thing is very interesting.

All of our tables are now “below the fold” when calling tableView:reloadData(). It’s not scrolling to the new first  index like it used to. When creating a new table, the rows do behave like expected, with the first row at position zero.

You can see in these two pictures how it’s happening. The table size is the white space in between the grey areas. If we tap on the table, the rows scroll to where they should be. It’s strange that the table’s rows are initializing below the visible table area.

We are currently solving this with a scrollToY = 0 on every tableView:reloadData() that needs it, but I’m just wondering if something changed, if it’s a bug, and what we can do about it?

Can anybody help with this? I read through all the changelogs and saw some widget work was done, and read the Docs on newTableView and reloadData but didn’t see anything new regarding this particular problem.

And note, we already have a workaround, it’s just annoying to have to do this when it would make more sense if the table rows loaded at y=0 based on how many rows there are when it is reloaded.

Thank you for your help, looking forward to learning about all the new Corona features in these daily builds!

Hi @georgeinspector,

Can you please test this with build 2015.2634 or earlier and report back if the same thing happens?

Thanks,

Brent

Hello Brent, thanks for the quick response. I’ve tested it, and whatever you were guessing must have been right. 2015.2634 does perform correctly in comparison to what was seen in 2014.2637.

Here is a picture of the comparison

Screen_Shot_2015_05_14_at_4_55_47_PM.png

Hi @georgeinspector,

Thanks for confirmation. Can I ask you to please file a bug report so that this issue enters our tracking system and can be assigned for investigation?

https://developer.coronalabs.com/content/bug-submission

Thank you,

Brent

Ok, submitted a bug report! Will look forward to up and coming fixes for the table view widget!

Thanks George,

Did you receive an automated response containing the bug case number? If so, can you please post that case # here? It helps for reference to others who may see this post.

Brent

Sure: Case 40714

EDIT: Here it is with the title as well: (Case 40714) TableView: ReloadData positions strangely, and DeleteRow lockups

Hi @georgeinspector,

Thanks for the details. There should be a fix for this in one of the upcoming daily builds.

Brent

They say they fixed the issue in daily build 2015.2644. I’ll be sure to check it out soon. Thanks for dealing with the problem! I’ve been using 2015.2634 in the meantime and it’s also working fine.

Hi @georgeinspector,

Can you please test this with build 2015.2634 or earlier and report back if the same thing happens?

Thanks,

Brent

Hello Brent, thanks for the quick response. I’ve tested it, and whatever you were guessing must have been right. 2015.2634 does perform correctly in comparison to what was seen in 2014.2637.

Here is a picture of the comparison

Screen_Shot_2015_05_14_at_4_55_47_PM.png

Hi @georgeinspector,

Thanks for confirmation. Can I ask you to please file a bug report so that this issue enters our tracking system and can be assigned for investigation?

https://developer.coronalabs.com/content/bug-submission

Thank you,

Brent

Ok, submitted a bug report! Will look forward to up and coming fixes for the table view widget!

Thanks George,

Did you receive an automated response containing the bug case number? If so, can you please post that case # here? It helps for reference to others who may see this post.

Brent

Sure: Case 40714

EDIT: Here it is with the title as well: (Case 40714) TableView: ReloadData positions strangely, and DeleteRow lockups

Hi @georgeinspector,

Thanks for the details. There should be a fix for this in one of the upcoming daily builds.

Brent

They say they fixed the issue in daily build 2015.2644. I’ll be sure to check it out soon. Thanks for dealing with the problem! I’ve been using 2015.2634 in the meantime and it’s also working fine.