Fixed
Status Update
No update yet.
Comments
mi...@gmail.com
Thanks! This looks like a bug, thank you for reporting!
ha...@google.com
mi...@gmail.com
I would also recommend setting the value to 10%. When you do that, the behavior is wild.
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.
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.
kl...@google.com
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
mi...@gmail.com
Any estimate on when will this release?
kl...@google.com
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.compose.foundation:foundation:1.8.0-alpha04androidx.compose.foundation:foundation-android:1.8.0-alpha04androidx.compose.foundation:foundation-jvmstubs:1.8.0-alpha04
ap...@google.com
Using the new version 1.8.0-alpha04 does not seem to resolve the issue for me. I tested with the same setting as the reported issue:
// it doesn't matter what you put here a the multiplier, the positionalThreshold is always 50%
positionalThreshold = { d -> d * 0.9f },
velocityThreshold = { Float.POSITIVE_INFINITY },
Description
Jetpack Compose version: BOM 2023.08.00 (Compose 1.5.0, I suppose)
Jetpack Compose component(s) used:
androidx.compose.ui:uiandroidx.compose.material3:material3Android Studio Build:
#AI-223.8836.35.2231.10671973, built on August 17, 2023Kotlin version:
223-1.9.0-release-358-AS8836.35.2231.10671973Steps to Reproduce or Code Sample to Reproduce:
basicMarqueewhich starts immediately with customvelocitywhich changes depending fromSlidercomponent.Slider. SometimesbasicMarqueestop working. The content is displayed but not scrolling. If I repeat - sometimes everything returns to normal, sometimes not.velocityfieldbasicMarqueesometimes does not work.Full code, just in case:
Visual demonstration:https://i.imgur.com/zeaIKfN.mp4