Mofe Ejegi
02/28/2024, 11:15 AMAndroidManifest.xml
.
<activity
android:exported="true" android:configChanges="orientation|screenSize|screenLayout|keyboardHidden|mnc|colorMode|density|fontScale|fontWeightAdjustment|keyboard|layoutDirection|locale|mcc|navigation|smallestScreenSize|touchscreen|uiMode"
android:name=".MainActivity"
>
Why is the activity given the responsibility of handling all possible config changes?
I've grown accustomed to handling config changes in all my years of Android development so I'm curious about the possible drawbacks of this approach, especially regarding fetching/updating resources (strings, drawables, etc).
Is there something unique about Compose Multiplatform (compared to the usual Android development) that allows this approach work well?Michael Paus
02/28/2024, 11:21 AMMofe Ejegi
02/28/2024, 11:23 AMMichael Paus
02/28/2024, 11:25 AMMofe Ejegi
02/28/2024, 11:33 AMStylianos Gakis
02/28/2024, 12:49 PMconfigChanges
before because it introduced problems. And all this has been in a pure compose app.Michael Paus
02/28/2024, 2:50 PMColton Idle
03/10/2024, 5:58 PMStylianos Gakis
03/10/2024, 6:17 PMColton Idle
03/10/2024, 6:28 PMMichael Paus
03/10/2024, 6:34 PMandroid:configChanges="orientation|screenSize|screenLayout|keyboardHidden|mnc|colorMode|density|fontScale|fontWeightAdjustment|keyboard|layoutDirection|locale|mcc|navigation|smallestScreenSize|touchscreen|uiMode"
which you get automatically when you create a new project with the Compose Multiplatform Wizard.Stylianos Gakis
03/10/2024, 6:41 PM