I posted this before the forum change but I guess all the old widget threads are gone?
Anyways, has the functionality of scrollToIndex changed. It seems to scroll to a relative value rather than an absolute value. so if you scroll to 5 twice, you’ll end up at row 10
I posted this before the forum change but I guess all the old widget threads are gone?
Anyways, has the functionality of scrollToIndex changed. It seems to scroll to a relative value rather than an absolute value. so if you scroll to 5 twice, you’ll end up at row 10
Hi!
Would you be so kind as to report a bug for this here: http://developer.coronalabs.com/content/bug-submission
I am working on widget bugs this week and would like to ensure that any outstanding bugs are reported so I can work through them.
Cheers 
Sure, Danny. done. case 21704
We greatly appreciate the new widget library and fixes - I know it’s a bit of a bear as well as a thankless job. Keep up the good work.
I posted this before the forum change but I guess all the old widget threads are gone?
Anyways, has the functionality of scrollToIndex changed. It seems to scroll to a relative value rather than an absolute value. so if you scroll to 5 twice, you’ll end up at row 10
Hi!
Would you be so kind as to report a bug for this here: http://developer.coronalabs.com/content/bug-submission
I am working on widget bugs this week and would like to ensure that any outstanding bugs are reported so I can work through them.
Cheers
Sure, Danny. done. case 21704
We greatly appreciate the new widget library and fixes - I know it’s a bit of a bear as well as a thankless job. Keep up the good work.
Hi Danny,
I downloaded the latest daily build since the docs reference this bug but it doesn’t seem to be fixed
Are you using daily build 1061?
yes
+1
bug still reproduces on 2013.1064 build
My bad, I didn’t fix that correctly at all.
Good news is that it is now properly fixed locally and I will try and get this fix into a daily build asap.
Apologies!
Hi Danny,
I downloaded the latest daily build since the docs reference this bug but it doesn’t seem to be fixed
Are you using daily build 1061?
yes
+1
bug still reproduces on 2013.1064 build
My bad, I didn’t fix that correctly at all.
Good news is that it is now properly fixed locally and I will try and get this fix into a daily build asap.
Apologies!