How does composables know about keyboard

[shalva97]

In your sample app, in the Text Fields controls if I focus a field and keyboard shows up then TextFields also scroll and appear above primary button

How does that work? on my app, with your components, this is the results

TextField is below the keyboard with textSelectHandle on top of it :D

Catalog app has android:windowSoftInputMode="adjustResize", but adding it on my app has no effect.

My layout is like this:

@Preview(showSystemUi = true)
@Composable
fun LoginScreen() {

    val viewModel: LoginScreenViewModel = hiltViewModel()

    var server by remember { mutableStateOf("192.168.") }

    val discoveredServer = viewModel.foundServers.collectAsState(initial = emptyList())

    Column(modifier = Modifier
        .systemBarsPadding()
        .fillMaxSize()
        .padding(10.dp),
        verticalArrangement = Arrangement.Bottom) {

        LazyColumn {
            items(discoveredServer.value.size) { index ->
                Card(onClick = { viewModel.connectToServer(discoveredServer.value[index]) }) {
                    Text(text = discoveredServer.value[index].address ?: "")
                }
            }
        }

        TextField(value = server,
            onValueChange = { server = it },
            label = { Text(text = "Server") },
            leadingIcon = { Icon(Icons.Trip, contentDescription = null) },
            modifier = Modifier.fillMaxWidth(),
            maxLines = 1)

        Button(onClick = { /*TODO*/ }, modifier = Modifier.align(Alignment.End), enabled = false) {
            Text(text = "Next", modifier = Modifier)
        }
    }
}

which is included inside OrbitTheme -> Scaffold -> Jetpack Navigation...

[hrach]

So are you using Orbit's TextField? If yes, there is the functionality to bring it into focus (see its source code).

We also utilize some measuring and Locals to add additional padding to bring the button above Scaffold's CTA.

[shalva97]

Yes, TextField is from Orbit. One thing I noticed is that, in the sample app, there is .verticalScroll(rememberScrollState()) modifier for Box. This is what I also dont have and without this the sample app also works like mine...

So is the verticalScroll needed including Scaffold?

Also could you please explain the expected layout for Orbit design? I was thinking about removing Scaffold entirely, but it looks like TextField sort of depends on Scaffold, right?

[hrach]

So is the verticalScroll needed including Scaffold?

I'm not sure I follow, but yes, scrollable parent is needed if you want to bring TextFiled above the keyboard.

Also could you please explain the expected layout for Orbit design? I was thinking about removing Scaffold entirely, but it looks like TextField sort of depends on Scaffold, right?

There is no requirement to use Scaffold to design a screen. You can be good with Column, Surface, ... Scaffold is a helper for bottom action layouting and topappbar layouting. At least for now.

[shalva97]

okay I found out what was going on. Accidentaly stumbled upon the docs for WindowManager.LayoutParams.SOFT_INPUT_ADJUST_RESIZE and it says I should manualy handle the window insets.

    /** Adjustment option for {@link #softInputMode}: set to allow the
     * window to be resized when an input
     * method is shown, so that its contents are not covered by the input
     * method.  This can <em>not</em> be combined with
     * {@link #SOFT_INPUT_ADJUST_PAN}; if
     * neither of these are set, then the system will try to pick one or
     * the other depending on the contents of the window. If the window's
     * layout parameter flags include {@link #FLAG_FULLSCREEN}, this
     * value for {@link #softInputMode} will be ignored; the window will
     * not resize, but will stay fullscreen.
     *
     * @deprecated Call {@link Window#setDecorFitsSystemWindows(boolean)} with {@code false} and
     * install an {@link OnApplyWindowInsetsListener} on your root content view that fits insets
     * of type {@link Type#ime()}.
     */

I think I am on a right track... will post update tomorrow

[shalva97]

1 week of stackoverflow, debugging, reading docs and this was all just one function call: .imePaddings() on Modifier... I hate android...