I just don't know why this has to be so difficult, in 2023.. If memory serves, going edge to edge in SwiftUI is a single line, and I can go focus on what I actually care about. When I throw Scaffold in the mix in ComposeUI, it's like I can't get a consistent behaviour if my child content changes (and yea I've taken note of the docs for contentPadding).
We're so glad you enjoyed this tutorial 😎 If you're interested in additional resources, feel free to scope out these helpful links below 🔍 : WindowInsets and IME Animations → goo.gle/compose-insets Insets for Jetpack Compose → goo.gle/3TX01EJ
Good catch, that is a mistake! For all devices I'm aware of, the status bar includes the space for the camera when oriented in portrait, so if you pad to avoid the status bar, you'll also avoid the camera. The point of safeDrawing is to have a type of insets that combines the other types in a useful way.
Thanks a lot for the video! I realized reverseLayout=true is the key to get lazycolumn scrolling with keyboard here. Is there simple way to achieve the same without reversing the list items?
@Android Developers Given the code at 4:50, how to properly request focus to TextField after keyboard scrolls in and later clear it when keyboard is gone? I tried using FocusRequester in tandem with WindowInsets.isVisible, however it fails due to "attempting to request focus during composition". Without this behaviour, I don't see any benefits to the user, if one still has to request focus to TextField by tapping. I've seen hacks involving coroutineContext.job.invokeOnCompletion, but I believe there must be a cleaner way. Apart from that, great API and video.
> Don’t be afraid to go edge-to-edge!
I'm still afraid, because coloring the status bar is so awkward.
Just the right time
I just don't know why this has to be so difficult, in 2023..
If memory serves, going edge to edge in SwiftUI is a single line, and I can go focus on what I actually care about.
When I throw Scaffold in the mix in ComposeUI, it's like I can't get a consistent behaviour if my child content changes (and yea I've taken note of the docs for contentPadding).
Gracias! Ya me hacia falta para controlar el teclado.
Hi Alex and thanks Google
We're so glad you enjoyed this tutorial 😎
If you're interested in additional resources, feel free to scope out
these helpful links below 🔍 :
WindowInsets and IME Animations → goo.gle/compose-insets
Insets for Jetpack Compose → goo.gle/3TX01EJ
So We dont need to use the accompanist insets anymore very useful
Very informative, thanks. I wouldn't mind a part 2.
We're glad that you have enjoyed the tutorial, Clement. Thanks for the feedback as well as 😁
It gets tricky when the hosting activity embeds compose, and has a native toolbar, specially when dealing with Compose's BottomSheet.
Nice!
How do I show a TextField in a LazyColumn with adjustResize? There is an open issue since 2 years ago
I am a programmer, what should I do to become an android developer.
I still can not using imePadding() modifier
I 💟 Android 😘❤️☺️
03:59 wait, camera is lower than status bar, does such a phone exist? And what's the point of safeDrawing?
Good catch, that is a mistake! For all devices I'm aware of, the status bar includes the space for the camera when oriented in portrait, so if you pad to avoid the status bar, you'll also avoid the camera.
The point of safeDrawing is to have a type of insets that combines the other types in a useful way.
It doesnt make sense for me at all !!! I think Manuel ahould go thro this once more .
Thanks a lot for the video! I realized reverseLayout=true is the key to get lazycolumn scrolling with keyboard here. Is there simple way to achieve the same without reversing the list items?
@Android Developers Given the code at 4:50, how to properly request focus to TextField after keyboard scrolls in and later clear it when keyboard is gone? I tried using FocusRequester in tandem with WindowInsets.isVisible, however it fails due to "attempting to request focus during composition". Without this behaviour, I don't see any benefits to the user, if one still has to request focus to TextField by tapping. I've seen hacks involving coroutineContext.job.invokeOnCompletion, but I believe there must be a cleaner way. Apart from that, great API and video.
Robeto José y