Hi, is this intended or a bug? I am using wear os ...

# compose-wear

[florent]

Hi, is this intended or a bug? I am using wear os scaffold and HorizontalPageIndicator, we can notice that on android studio running device preview it looks ok however on the device the indicator circle is cut. The more I test my composables between the Samsung galaxy watch 4 and the Pixel Watch it seems that their notion of screen size is different, I was expecting compose to abstract that complexity from me. Is it still something being worked on? Thanks 🤗

[Arjun Achatz]

Hmm .. I'm using this widget as well, but it works as expected for me. I'm using fillMaxSize for my pages though

[Arjun Achatz]

I didn't see my indicator dots being cut, but I did offset my circles by 10dp

[yschimke]

Are you using HorizontalPager from accompanist and PageIndicator from Wear Compose?

[yschimke]

Horologist has a WearPager that combines them, applies the right 10dp padding and also crops to circle for when you swipe between. If you can reproduce with WearPager, even just to confirm your problem. Then I can fix the bug if any

[florent]

I use the one from wear compose. I had a look at the one from horologist but it uses a snap library from accompanist that is now deprecated.

[yschimke]

Thanks for flagging.

[florent]

So I guess that spacing is gonna be fixed on a newer wear compose version?

[yschimke]

I don't think so, I believe you can just apply the padding.

[florent]

It is a bit weird to have both the components on horologist and wear compose

[yschimke]

I asked this, and believe I got told to apply the padding.

[yschimke]

Horlogist uses wear compose pageindicator.

[yschimke]

But wear compose can't depend on accompanist, while horologist can

[yschimke]

I don't think their is any duplicated pager related code or functionality between them

[yschimke]

@florent which is the snap library? We use Accompanist HorizontalPager, which still uses Chris Banes' Snapper. But that project is archived because of core Compose's SnapFlingBenhaviour in 1.3.0.

[yschimke]

Which one are you using that doesn't use that?

[yschimke]

Archived project: https://github.com/chrisbanes/snapper

[yschimke]

Usages in Accompanist https://github.com/google/accompanist/search?l=Kotlin&q=snapper&type=code

[florent]

I built my own pager using compose 1.3 snapflingbehavior. Snapper is the one that for me is deprecated now

[yschimke]

Hardcore :)

[florent]

Hehe 😁

[florent]

It is not really hardcore in practice, I see that more as an investment to understand compose api

[yschimke]

I've raised this for accompanist https://github.com/google/accompanist/issues/1419, I don't think it's great to expect everyone to implement their own custom pager, since there is a lot of subtle UX to get this right.

[yschimke]

BTW I lied about the padding for the indicator, it's 6.dp here https://github.com/google/horologist/blob/37fe1b9366eb8dad344935195002662847158f22[…]java/com/google/android/horologist/compose/pager/PagerScreen.kt

[florent]

2 dp was enough for my case