Problem with TableView:scrollToIndex()

Solar2D Advanced Graphics
#1

Hi.

I am working on migrating my code to the new api, and found out some things that are not working for me.

I am having problems using the scrollToIndex of the tableview. Seems to me that is still not using the new center anchors… because if you call scrollToIndex, the rows are being positioned from the center of the tableview. 

You can easily test this by opening the ListView1 sample code and add list:scrollToIndex(1,0) at the very end of main.lua file, after the for loop where the rows are inserted.

Any info about this? 

Also… if this is fixed in daily builds… where can the starter users get it ?

Thanks!

#2

Good catch. I also see the same on my end. Interesting thing though is when I use 0 for the time (optional) parameter as you mention the scrollToIndex does not work at all. Nothing happens. When I put in a value greater than 0, even 1 will do, then the scrollToIndex work and it works wrongly in the manner you describe again. So the time issue might be another bug in there. 

#3

I have no problem using 0 as the time param. It scrolls fine, only that is offsetted by half the height.

#4

This is very interesting as we are both using the same sample to verify the initial bug that you discovered. I have no idea why we would see different behavior on the time delay parameter but 0 is definitely not working on this end. 2 bugs that need to be looked at then.

#5

I added this entry to the tracking spreadsheet, to be investigated. Thanks for the heads up.

#6

Sorry to hijack.

@Brent, not sure what tracking spreadsheet you are referring to but can you please check this and possibly add it? http://forums.coronalabs.com/topic/41488-tableview-layout-bug-when-having-defined-defaults-for-anchorx-and-anchory/

This bug is a stopper for me and anyone that decided to put top left as default anchor position and using a tableview.

#7

I think he is referring to my humble issues tracking spreadsheet. It can be found at : 

docs.google.com/spreadsheet/ccc?key=0AsuRVbWElS3YdGpCN0V3emtmWnlwQmRUOVlpb3RkOGc&usp=sharing

also the thread where this list was introduced is here : 

http://forums.coronalabs.com/topic/37217-list-of-open-widget-20-bugs-promised-features/page-3#

It offers great visibility to open issues. Kindly take a moment to enter your bug in there if you can. Thanks much!

#8

Ok added :slight_smile:

#9

Any luck in reproducing the issue? Hope to see a fix for this one soon. 

#10

Hey guys,

The fix for this will be available in a daily soon.

Thanks,

alex

#11

Super. Thanks for letting us know. This one was a show-stopper. 

#12

Good catch. I also see the same on my end. Interesting thing though is when I use 0 for the time (optional) parameter as you mention the scrollToIndex does not work at all. Nothing happens. When I put in a value greater than 0, even 1 will do, then the scrollToIndex work and it works wrongly in the manner you describe again. So the time issue might be another bug in there. 

#13

I have no problem using 0 as the time param. It scrolls fine, only that is offsetted by half the height.

#14

Hi guys, 

any idea when this might be on the open source code for the widgets on github? Otherwise i will need to wait until the next public release for this fix.

Thanks

#15

This is very interesting as we are both using the same sample to verify the initial bug that you discovered. I have no idea why we would see different behavior on the time delay parameter but 0 is definitely not working on this end. 2 bugs that need to be looked at then.

#16

I added this entry to the tracking spreadsheet, to be investigated. Thanks for the heads up.

#17

Sorry to hijack.

@Brent, not sure what tracking spreadsheet you are referring to but can you please check this and possibly add it? http://forums.coronalabs.com/topic/41488-tableview-layout-bug-when-having-defined-defaults-for-anchorx-and-anchory/

This bug is a stopper for me and anyone that decided to put top left as default anchor position and using a tableview.

#18

I think he is referring to my humble issues tracking spreadsheet. It can be found at : 

docs.google.com/spreadsheet/ccc?key=0AsuRVbWElS3YdGpCN0V3emtmWnlwQmRUOVlpb3RkOGc&usp=sharing

also the thread where this list was introduced is here : 

http://forums.coronalabs.com/topic/37217-list-of-open-widget-20-bugs-promised-features/page-3#

It offers great visibility to open issues. Kindly take a moment to enter your bug in there if you can. Thanks much!

#19

Ok added :slight_smile:

#20

Any luck in reproducing the issue? Hope to see a fix for this one soon.