scrolling widget batshit insane on android

Well, the scrolling widget is impossible to control on some android devices, it scrolls absurdly fast, and by absurdly fast I mean that sometimes you move your finger 1 milimeter and the thing jump so hard that the next frame you see nothing and then 1 frame later you see the thing rebounding back…

How I fix that?

Or how Corona fix that?

I am using the lastest release (not daily build) [import]uid: 142895 topic_id: 31144 reply_id: 331144[/import]

You should not using widget ScrollView. Sometimes it can disappear with all your content inside.
They know about this bug. You should wait. They are very slow in fixing this things.
Try to use this http://developer.coronalabs.com/code/scroll-content
It is not perfect but I think it doesn’t have that bug.
[import]uid: 138389 topic_id: 31144 reply_id: 124599[/import]

And here we go with Corona disappointing me a lot again…

First, scroll content is no good to me, I am using it only in part of the screen, not the whole screen…

And second, I used ScrollView because of a very bizarre behavior when I tried to do my own version (ie: when I inserted object C in customscrollview B inside group A and moved group A by 20 and scrollview B by 20, the result was B moving 20 and A moving 40).

Corona :frowning: [import]uid: 142895 topic_id: 31144 reply_id: 124606[/import]

>>>I used ScrollView because of a very bizarre behavior when I tried to do my own version …
You should post here your code. I can’t say nothing about this.
Maybe there was an error somewhere. [import]uid: 138389 topic_id: 31144 reply_id: 124613[/import]

Hey Stan.

We are aware of this issue and are working on a fix. I don’t have a time estimate at present but I can assure you that it is being worked on and that we take any bugs with our SDK very seriously.

The fix will be here sooner rather than later, and by that i don’t mean it’s going to take months.

Sit tight and I will get this fixed asap. [import]uid: 84637 topic_id: 31144 reply_id: 124723[/import]

Thanks :slight_smile:

The faster, the better! Because the app that uses scrollview is already gold and we are already uploading it to the markets… (only waiting for apple approval to launch in all markets at the same time…) [import]uid: 142895 topic_id: 31144 reply_id: 124725[/import]

Your welcome Stan, although I don’t need the thanks. This issue has been outstanding for a long time (I have only just taken over development of the widget library however).

I will keep you posted. [import]uid: 84637 topic_id: 31144 reply_id: 124726[/import]

You should not using widget ScrollView. Sometimes it can disappear with all your content inside.
They know about this bug. You should wait. They are very slow in fixing this things.
Try to use this http://developer.coronalabs.com/code/scroll-content
It is not perfect but I think it doesn’t have that bug.
[import]uid: 138389 topic_id: 31144 reply_id: 124599[/import]

And here we go with Corona disappointing me a lot again…

First, scroll content is no good to me, I am using it only in part of the screen, not the whole screen…

And second, I used ScrollView because of a very bizarre behavior when I tried to do my own version (ie: when I inserted object C in customscrollview B inside group A and moved group A by 20 and scrollview B by 20, the result was B moving 20 and A moving 40).

Corona :frowning: [import]uid: 142895 topic_id: 31144 reply_id: 124606[/import]

>>>I used ScrollView because of a very bizarre behavior when I tried to do my own version …
You should post here your code. I can’t say nothing about this.
Maybe there was an error somewhere. [import]uid: 138389 topic_id: 31144 reply_id: 124613[/import]

Hey Stan.

We are aware of this issue and are working on a fix. I don’t have a time estimate at present but I can assure you that it is being worked on and that we take any bugs with our SDK very seriously.

The fix will be here sooner rather than later, and by that i don’t mean it’s going to take months.

Sit tight and I will get this fixed asap. [import]uid: 84637 topic_id: 31144 reply_id: 124723[/import]

Thanks :slight_smile:

The faster, the better! Because the app that uses scrollview is already gold and we are already uploading it to the markets… (only waiting for apple approval to launch in all markets at the same time…) [import]uid: 142895 topic_id: 31144 reply_id: 124725[/import]

Your welcome Stan, although I don’t need the thanks. This issue has been outstanding for a long time (I have only just taken over development of the widget library however).

I will keep you posted. [import]uid: 84637 topic_id: 31144 reply_id: 124726[/import]

At least on Kindle Fire, setting the friction to 0.1 seems to have helped keeping the scrollview under control. [import]uid: 39505 topic_id: 31144 reply_id: 125550[/import]

hawkwood thanks!

The behavior now kinda suck, but now it is usable…

The low friction is kinda obvious (you need to drag a lot to go where you want), but it avoids the batshit insane scrolling issue, now it only scroll as you wish. [import]uid: 142895 topic_id: 31144 reply_id: 125582[/import]

The bug is there when you are using 0.1 friction but will not see it thery often.
With 0.1 friction this is not scrolling but moving. [import]uid: 138389 topic_id: 31144 reply_id: 125635[/import]

At least on Kindle Fire, setting the friction to 0.1 seems to have helped keeping the scrollview under control. [import]uid: 39505 topic_id: 31144 reply_id: 125550[/import]

hawkwood thanks!

The behavior now kinda suck, but now it is usable…

The low friction is kinda obvious (you need to drag a lot to go where you want), but it avoids the batshit insane scrolling issue, now it only scroll as you wish. [import]uid: 142895 topic_id: 31144 reply_id: 125582[/import]

The bug is there when you are using 0.1 friction but will not see it thery often.
With 0.1 friction this is not scrolling but moving. [import]uid: 138389 topic_id: 31144 reply_id: 125635[/import]

Any update on this? It’s annoying to have to change friction to 0.1 for android builds. It also looks shoddy. [import]uid: 94304 topic_id: 31144 reply_id: 127319[/import]