Mitchell Syer

I made a quick and dirty implementation of this for my application, if you need it feel free to copy/improve upon my implementation. https://github.com/Suwayomi/Tachidesk-JUI/blob/master/ui-core/src/desktopMain/kotlin/ca/gosyer/jui/uicore/components/DesktopScrollbar.kt#L80

I was investigating this, and I think it may be because the lifecycle is not bound to the screen, but the activity. Even when I am using AndroidScreen screens, which...

I did some more investigating with it, and I tested providing the screen lifecycles to the content and noticed it was not working either. I found that the screens lifecycle...

Hmm, I don't think its working. The lifercycle observer is still isnt saving data into the bundle.

Try this, `object SearchScreen : Screen` should be `class SearchScreen : AndroidScreen()` and you should use remember { SearchScreen() } if this is your initial screen in the navigator. I...

Something like `Navigator(remember { HiltListScreen() })` Its a safeguard because Compose can re-create classes based on parent composables.

Ok I did some testing and this bug seems to be related to the changes done in 1.0.0-rc01, it doesnt happen in 1.0.0-beta16. So I guess use 1.0.0-beta16 for now...

I did my own port of Compose Material Dialogs to Compose Multiplatform https://github.com/Syer10/compose-material-dialogs Feel free to take from it as well. I have ported version 0.20.0 of [Accompanist to Compose...

Yep, just click one of the links in the readme and it will show you the implementation instructions

Currently my Accompanist and material dialog forks use a shared Jvm main, so nothing is exposed to common. My application does the same so I haven't put in the work...