-
Notifications
You must be signed in to change notification settings - Fork 75
Fixed the space or rebound issue #4146
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
base: master
Are you sure you want to change the base?
Conversation
Pull Request Test Coverage Report for Build 18618380989Details
💛 - Coveralls |
|
Rule of thumb, if you are fixing/working on UI show us how it looks/works :) |
|
I was building the ios still to take the screenshot, was about to attach. Anyway, thanks for the heads-up @Withalion |
75c3747 to
eb72e98
Compare
Withalion
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The "spacer" id is not necessary. Let's see what @tomasMizera thinks about it.
tomasMizera
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @kaustuvpokharel, so which of the two cacheBuffer/snapMode fixed the issue? :)
The cacheBuffer fixed it here, and I am explicitly using snapMode which is helping to fall to contentItem on view and not anywhere random i.e. empty spaces or such, so I have kept it for cleaner and safer approach. |
1ac6106 to
941a670
Compare
941a670 to
ebd8386
Compare
📦 Build Artifacts Ready
|
📦 Build Artifacts Ready
|
Case: In featureList whenever flickable is scrolled fast or scrolled out of bound; it rebounds and parks the feature below the "add feature" button awkwardly.
FIx: delete the cachedBuffer altogether. In addition, when scrolling up really fast, the list used to go out of bounds, to fix this I added a threshold for the verticalOvershoot and made the list come back to the first element.
ScreenRecording_12-19-2025.13-40-17_1.MP4
And also tested on MacOS, with the project which was referred in this ticket :
Enregistrement.de.l.ecran.2025-12-19.a.18.02.05.mov