Ivan Matkov
Ivan Matkov
I intentionally avoided `DisposableEffect` usage here because it might be called after disposing `rememberSaveable` itself (it removes it from saving list). By "manually" I meant calling it outside of compose...
> how do you know when you should call it then? I thought about a general case with `ComposePanel` when you have direct control of disposing it/Compose. > When I...
> It has to be in the root Composable right Ivan? No, it's regular compose local and might be applied/replaced only to part of your application. I didn't test it...
[Compose Navigation](https://github.com/JetBrains/compose-multiplatform-core/pull/1219) [provides](https://github.com/JetBrains/compose-multiplatform-core/blob/11552ff6c005be51ab682964465981db8de562e3/navigation/navigation-compose/src/main/java/androidx/navigation/compose/NavHost.kt#L362) `LocalSaveableStateRegistry` inside `NavHost`, so `rememberSaveable` restores its state after navigating back to the previous screen. It's available in the latest dev, and I'm considering it as a...
It should be mitigated after implementing [smooth (animated) scrolling](https://github.com/JetBrains/compose-multiplatform-core/pull/438), but if you need to check if there was a scroll, you should subscribe to `firstVisibleItemIndex` and `firstVisibleItemScrollOffset` (as @SebastianAigner mentioned...
It worth to mention that [smooth (animated) scrolling](https://github.com/JetBrains/compose-multiplatform-core/pull/438) is merged, so currently there is a [TODO](https://github.com/JetBrains/compose-multiplatform-core/blob/abd75ea142aa1c13dd2fc6183b7c0beeb6a0f681/compose/foundation/foundation/src/commonMain/kotlin/androidx/compose/foundation/gestures/Scrollable.kt#L350-L358) in code about this flag. Please note that it's still not exactly about mouse...
@aljohnston112 It's about #3366. Fixed in https://github.com/JetBrains/compose-multiplatform-core/pull/696 It was because conflicting simultaneous animations (triggered by mouse wheel and by your `scrollToItem`)
It's currently not supported. As I see, it's not implemented in an underlying skia library either. On Android, Compose uses a system line breaker for this.
It's expected because `kotlinx-coroutines-swing` is optional. I'll check why a warning message is missed + make sure that it's desired in docs
Fixed in 1.6.10-rc03