Open rprusa opened 1 month ago
"Apps using Material 3 Compose components might not be negatively impacted because most components apply insets. Apps using Material 2 Compose components might be negatively impacted because Material 2 components don't automatically apply insets."
Now, I'm too stupid to understand what that actually means, but I wanted to see if perhaps just changing the targetSdk would automatically make NeoStumbler display as shown in the documentation. I went into Android Studio, opened build.gradle changed targetSdk to 35, ran Gradle Sync, and ran the app inside an API 35 emulator. This did not make NeoStumbler display edge-to-edge, but it also didn't break the UI in any immediately noticeable way.
This is what the tab looks like after another week:
There are a few very minor purely cosmetic issues with the Statistics tab, some of these are my suggestions, and subject to personal preference. Neither of these issues in any way impacts the core functionality of the app, or it's usability in meaningful ways.