Anyone from the wear-compose team ? Why is this me...

# compose-wear

[Morgan]

Anyone from the wear-compose team ?
Why is this method private ?
Will this be available in a future update ? Because at the moment, if we want to change the sensitivity, we must use the other method that takes a ScrollableState and provide a LayoutInfoProvider on our own.
Also, we cannot customize the sensitivity beyond these 2 values that are HIGH and DEFAULT

@Composable
    private fun snapBehavior(
        scrollableState: ScrollableState,
        layoutInfoProvider: RotarySnapLayoutInfoProvider,
        snapSensitivity: RotarySnapSensitivity,
        snapOffset: Dp,
        hapticFeedbackEnabled: Boolean
    ): RotaryScrollableBehavior

[yschimke]

As a general principle, Androidx is very cautious about new public APIs, just because they may be useful. I think there is an expectation that copy paste reuse is better than regretted public APIs

[yschimke]

But raise a bug with what you need and why. Is the sensitivity change device specific?

[marlonlom]

@Morgan how do you use that function in your wearos app?
Maybe do as @yschimke and share more contexto about your questions 👍🏼

[Morgan]

Yes, we would like to customize the sensitivity across the device which is our own device.
But even without this, is there a specific reason about why the Pager sensitivity is set to HIGH and the ScalingLazyList to DEFAULT ?
I find it difficult to scroll with the crown on a pager and to target a specific item

[Morgan]

@marlonlom I'm using this on a HorizontalPager
The sensitivity is way too high to properly select an item or at least this is the case for us