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
How to increase swiping speed in swiper example #36
Comments
|
That's what pretty much the framework offers so there is no direct way of doing it as of now. However it should just work fine when you scroll fast if you don't have heavy data. |
No actually it doesn't scroll more than 2-3 items. Even with your Boxes/Container() - which are very light. May be because of pageView, it's not possible. |
I will take a look into it. It can be a good use case. Swiper is generally
used for 9-10 items most of the time though.
…On Sat, 7 Nov 2020 at 2:41 PM, Virat Shukla ***@***.***> wrote:
No actually it doesn't scroll. Even with your Boxes/Container() - which
are very light.
Looks like, it is property of PageView. That at most 2-3 items are
scrolled. While in other like horizontal list view, items are scrolled very
fast.
May be because of pageView, it's not possible.
Can we implement the same behaviour (At a time, 1 is highlighted and it
should auto-scroll in middle when finger is removed from screen) with
ListView?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#36 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADAI5HCXNUTJFLRVIXY6LUDSOUFLZANCNFSM4TM4II4Q>
.
|
Added a new flag "isFastScrollingEnabled" to scroll the page view even faster. Closing on behalf of 4de9f6e |
@viratshukla Can you try it now once? |
For example, we have large number of horizontal content to be scrolled.
And it should be in same manner - like item should always come to middle after scrolling. Currently with swiper, it hardly scrolls 2-3 views at a time, which is really inconvenient.
Any suggestion to increase the scrolling speed?
The text was updated successfully, but these errors were encountered: