We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently iOS samples use constant offset from the top to show the content.
Instead we should calculate top bar height (that is different for different devices) and use it as offset.
The calculation should be done automatically and embedded to androidx.compose.ui.window.Application.
androidx.compose.ui.window.Application
We probably also need a new parameter - topBarColor in this function to automatically color the top bar.
topBarColor
Then all iOS samples should b fixed to remove current constant offset workaround.
The text was updated successfully, but these errors were encountered:
Isn't that approach a little bit too simplistic? See for example: https://blog.felgo.com/cross-platform-app-development/notch-developer-guide-ios-android
Sorry, something went wrong.
Useful links. How it works on Android: /Users/dim/Desktop/github/dima-avdeev-jb/android-intets Experiments on iOS: JetBrains/compose-multiplatform-core@36d9f9a
Done in this PR:
Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.
mazunin-v-jb
No branches or pull requests
Currently iOS samples use constant offset from the top to show the content.
Instead we should calculate top bar height (that is different for different devices) and use it as offset.
The calculation should be done automatically and embedded to
androidx.compose.ui.window.Application
.We probably also need a new parameter -
topBarColor
in this function to automatically color the top bar.Then all iOS samples should b fixed to remove current constant offset workaround.
The text was updated successfully, but these errors were encountered: