Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FastScroller handle sync delay #605

Closed
tcqq opened this issue May 4, 2018 · 3 comments
Closed

FastScroller handle sync delay #605

tcqq opened this issue May 4, 2018 · 3 comments

Comments

@tcqq
Copy link

tcqq commented May 4, 2018

@davideas Now the Item position is at the top, when the Item scrolls down a distance, the position of the scroll bar does not change
image
image

Scroll bar changes when Item scrolls a long distance, But I can be sure that the above problem is not because of too many items, Because when I continue to scroll down, the scroll bar changes slightly, I feel the synchronization delay of scroll bars may be related to app:layout_behavior="@string/appbar_scrolling_view_behavior", although appbar_scrolling_view_behavior is set, but the FastScroller not remove the excess height for scroll bar, causing the first scroll sync delay.
image

@davideas davideas added the bug label May 10, 2018
@davideas
Copy link
Owner

davideas commented May 10, 2018

@tcqq, thank for this issue, I see it.
The FastScroller comes from another library. I verified the issue comes from there, and is still there! The calculation is done in setBubbleAndHandlePosition(y) and the effect is more visible at the increase of the items, the handle doesn't move along with the positions when at the top or at the bottom. Indeed it is caused by the wrong usage of the height of the handle.

@davideas
Copy link
Owner

davideas commented May 10, 2018

It should be fixed now, can you please check? Lines 427-429.

@davideas davideas changed the title FastScroller scroll bar sync delay FastScroller handle sync delay May 10, 2018
@tcqq
Copy link
Author

tcqq commented May 10, 2018

@davideas Hi, I tested it, this problem looks has been fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants