ynsok
04/12/2022, 8:51 AMBig Chungus
04/12/2022, 9:20 AMynsok
04/12/2022, 9:53 AMGrégory Lureau
04/12/2022, 9:55 AMynsok
04/12/2022, 11:16 AMGrégory Lureau
04/12/2022, 2:09 PMAdam Powell
04/12/2022, 2:18 PMrememberSaveable
and the associated family of APIs are already mpp configuredLandry Norris
04/12/2022, 3:06 PMZach Klippenstein (he/him) [MOD]
04/14/2022, 4:41 PM<https://developer.android.com/reference/kotlin/androidx/compose/runtime/saveable/SaveableStateRegistry|SaveableStateRegistry>
implementation that saves to a file or something.Adam Powell
04/14/2022, 5:59 PMZach Klippenstein (he/him) [MOD]
04/14/2022, 6:06 PMSaveableStateHolder
) there's no serialization and the restoration is already implemented purely in memory, so I would expect that to already Just Work for desktop. If that's not the case, it sounds like a bug.Adam Powell
04/14/2022, 6:10 PMrememberSaveable
remembers state across conceptual task close operations, which is generally part of what closing a desktop app process means, but that's not the API contract of rememberSaveable
Adam Powell
04/14/2022, 6:11 PMAdam Powell
04/14/2022, 6:13 PMTrejkaz
12/27/2024, 10:21 AMSaveableStateHolder
, it did seem to trigger a call to save() on my saver at least, but only once, and it was never clear how to get it to call it again, and I also never saw it call restore()Trejkaz
12/27/2024, 10:22 AMLocalSaveableStateRegistry
really seemed to be the viable workaround but it was a bit too much work for me at the time. trying to write apps, not implement large portions of the app framework 😞Trejkaz
12/27/2024, 10:22 AMPreferences