Status Update
Comments
ti...@google.com <ti...@google.com> #2
Thanks! This looks like a bug, thank you for reporting!
mo...@google.com <mo...@google.com> #3
Dragging up to 10% or between 50% and 90% will cause it to snap back to the start anchor.
Dragging between 10% and 50% or past 90% will cause it to snap to the end anchor.
le...@google.com <le...@google.com> #4
Project: platform/frameworks/support
Branch: androidx-main
Author: Jossi Wolf <
Link:
Update AnchoredDraggable target calculation logic
Expand for full commit details
Update AnchoredDraggable target calculation logic
We were previously relying on currentValue and the next closest anchor in the drag direction, but the simpler and more reliable way is to look at the left and right anchors as the window.
Relnote: Fixed a bug where positional thresholds passed to AnchoredDraggableDefaults.flingBehavior were not considered correctly in some scenarios.
Test: anchoredDraggable_fling_offsetPastHalfwayBetweenAnchors_beforePosThreshold_doesntAdvance
Bug: 367660226
Bug: 366003852
Change-Id: Ifdf0dfcf3d7ff8288affee56e7092bbed473d6ab
Files:
- M
compose/foundation/foundation/src/androidInstrumentedTest/kotlin/androidx/compose/foundation/anchoredDraggable/AnchoredDraggableStateTest.kt
- D
compose/foundation/foundation/src/androidInstrumentedTest/kotlin/androidx/compose/foundation/anchoredDraggable/AnchoredDraggableTestState.kt
- M
compose/foundation/foundation/src/commonMain/kotlin/androidx/compose/foundation/gestures/AnchoredDraggable.kt
Hash: eff53304942e9fd4fa5382e0cf487a734c5b8d28
Date: Thu Sep 19 16:24:55 2024
sl...@gmail.com <sl...@gmail.com> #6
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.compose.foundation:foundation:1.8.0-alpha04
androidx.compose.foundation:foundation-android:1.8.0-alpha04
androidx.compose.foundation:foundation-jvmstubs:1.8.0-alpha04
lp...@google.com <lp...@google.com>
le...@google.com <le...@google.com>
lp...@google.com <lp...@google.com>
ma...@gmail.com <ma...@gmail.com> #7
ap...@google.com <ap...@google.com> #8
Same. I've run this again on 1.8.0-alpha04. When using
positionalThreshold = { d -> d * 0.1f }
Dragging up to 10% or between 50% and 90% will cause it to snap back to the start anchor. Dragging between 10% and 50% or past 90% will cause it to snap to the end anchor.
I would expect It to only return if dragged less than or equal to 10% and snap to the end if dragged greater than 10%.
When using
positionalThreshold = { d -> d * 0.9f }
It acts as if the threshold has been set to 50%.
From what I can tell, nothing has changed about the behavior.
pr...@google.com <pr...@google.com> #9
Thanks, we will investigate and update this issue.
Description
Android Studio Build: 2021.1.1 RC 1 Bumblebee
Kotlin version: 1.6.10
There is no way we can implement custom Overscroll Effects for the Colum/Row Composable in Jetpack Compose. The OverScrollController argument in the Modifier.scrollable function is private!! For normal Views using XML, we are using CoordinatorLayout.Behavior, but with Compose there are no such implementation!
When I try to implement it my self using pointerInteropFilter to get the events combined with verticalScroll fro the scrolling. But there is no way to manually control the scroll the Composable. And the scroll is lagging, since using both combined interact with them self, obviously both consume the events and that leads to lagging, and not correctly register the touch events using pointerInteropFilter .