I’m seeing some behavior that I think might be a bug. It seems like `LayoutModifier`s are only being calculated when they’re first applied to a node, and any changes in subsequent compositions don’t actually update the layout. E.g. I’m trying to move a composable around by passing a custom

Alignment

implementation that just takes a fraction and aligns to that fraction of the parent. The initial alignment is calculated correctly, but when the fraction changes in subsequent compositions, the composable’s position doesn’t change. Will file soon.

Noticing some weird behavior where my UI tests pass on the emulator but fail on the device. I’m doing a super basic check -

composeTestRule.onNodeWithText("Title").assertExists()

Crashed when using

webContext.goBack()

to handle back press in WebView.

java.lang.IllegalStateException: KeyEvent can't be processed because this key input node is not active.

at androidx.compose.ui.input.key.KeyInputModifier.processKeyInput(KeyInputModifier.kt:62)

at androidx.compose.ui.platform.AndroidComposeView.sendKeyEvent(AndroidComposeView.kt:196)

at androidx.compose.ui.platform.AndroidComposeView.dispatchKeyEvent(AndroidComposeView.kt:200)

Is something wrong? I remember it won't crash before.

What’s the replacement for

Modifier.align

on alpha 4?

What are simple samples showing the power of kotlin compiler plugin for jetpack compose, enabling language constructs not possible with standard kotlin language? I am preparing a talk about kotlin compiler plugins and jetpack compose comes as the first on my mind …

Is there an example of animating away a list item? I’m using SwipeToDismiss and it animates the previous item in the list when recovering. Here’s the relevant code:

In other words, is it even possible to reset the applied Modifiers? Like in CSS? It can be useful to tweak existing composables components

Anyone tried getting the following error when using ScrollableColumn composable: (version: ‘1.0.0-alpha04’)

java.lang.IllegalStateException: Reading a state that was created after the snapshot was taken or in a snapshot that has not yet been applied

Hi, what am I doing wrong here? I am trying to use the SpaceBetween arrangement but both Strings are stuck on the left of my screen:

@Composable
fun PriorityOptions() {
    ScrollableColumn(
        modifier = Modifier.fillMaxWidth()
            .fillMaxHeight()
            .padding(start = 20.dp, end = 20.dp),

        ) {
        Spacer(Modifier.preferredHeight(50.dp))
        Text(text = "Priority Options", style = typography.h1)
        Spacer(Modifier.preferredHeight(50.dp))
        Row(horizontalArrangement = Arrangement.SpaceBetween) {
            Text("Start")
            Text("End")
        }
    }

How can I detect if software keyboard is visible in the screen or not?

Compose Text Team there is a wrong copy/paste here :

Is there a console logger (like Logcat) to Compose Preview? I would like to log/print some Compose behaviors without deploy to a device.

Documentation is broken? All the examples there show

//Unresolved: androidx.compose. …

https://developer.android.com/reference/kotlin/androidx/compose/animation/package-summary#animate

Can someone from the core team share insight on the reason for the name change? Coming from SwiftUI, Stack is quite familiar nomenclature!

Text

composable when not placed in a

Surface

seem to not apply

Material Theme

correctly. So when I do:

Column {
    Text()  // This text color is black in both light and dark theme
}

It seems that

ContentAmbientColor

is not properly set for

onBackgroundColor

(composables not part of a surface). Its really hard to trace what exactly is the problem though, as routing to sources in the IDE is currently broken.

How to make scrollbars in a ScrollableRow always visible. I am looking for something like android:fadeScrollbars="false".

If a parent compose collect a

Flow

from

ViewModel

as

state

and it’s multiple children also collect the same flow as state then would it hamper the performance? I have TextFields in different layer. So passing state would make the code messy. Thats why wanted to collect the same flow from multiple Composables.

I am trying to move to compose 1.0.0-alpha04 and I have updated the new compiler dependency androidx.compose.compiler:compiler:1.0.0-alpha04 but still I am getting the below error, any idea why?

Execution failed for task ':app:prepareDebugKotlinCompileTask'.

> Could not resolve all files for configuration ':app:kotlin-extension'.

> Could not find androidx.compose:compose-compiler:1.0.0-alpha04.

you need to update AGP to alpha13

I was reading that in 1.0.0-alpha04, the

LazyColumnFor

issue about remembering the scrolling position was fixed. But I just checked and it’s not, at least not automatically. My use case is very simple: a list of elements; click on one element to display the detail page; going back to the list; the position is reset to the top, and not kept So, do we need to explicitly set that it should be remembered? And How? I mean that would be strange, as in the normal Android view system, the list scroll position is remebered when you go back to the list screen.

Does the LazyItemScope work like a Column? It seems so. Wondering if I need to wrap content of item in a Column or call

item{}

multiple times, since it says

Adds a single item to the scope.

in the doc.

LazyColumn {
   item { Text("Title") }
   item { Header() }
   items(items) { ... }
}
// or
LazyColumn {
   item {
      Text("Title)
      Header()
   } 
   items { ... } 
}

I’ve been stuck on this error for like 8 hours. I have a simple component

@Composable
fun EmailTextField() {
    val viewModel = viewModel<AuthenticationViewModel>()
    val text: String by viewModel.email.observeAsState("")
    TextField(
        value = text,
        onValueChange = viewModel::setEmail,
        label = { Text(text = "What's your email address?") },
        placeholder = { Text(text = "<mailto:jane.doe@gmail.com|jane.doe@gmail.com>") },
        keyboardType = KeyboardType.Email,
        modifier = frameFillWidth(60.dp)
    )
}

The context it’s called in is this:

@Composable
fun SignInEmailView() {
    SingleInputLayout(
        onBackClicked = {},
        onNextClicked = {},
        children = {
            EmailTextField()
        }
    )
}

and I get the error:

e: java.lang.IllegalArgumentException: Unbound type parameters are forbidden: [Unbound private symbol org.jetbrains.kotlin.ir.symbols.impl.IrTypeParameterSymbolImpl@124a0920, Unbound private symbol org.jetbrains.kotlin.ir.symbols.impl.IrTypeParameterSymbolImpl@6e295b2d]

I’ve been able to isolate this error to the

EmailTextField

view and when I comment it out the error goes away. I’ve tried reproducing in a sample project but have been unable to do so. Does anything in the example I’ve provided seem off? compose: 1.0.0-alpha04 kotlin: 1.4.10

Is the EAP version of kotlin (1.4.20-M1) compatible with alpha04?

How to align two Text composables by a baseline?

Is it possible to get a compose dialog to appear fullscreen without padding?

I am starting to experiment with drag and drop in compose. A view is made draggable by implementing the dragGestureListener and then modifying the x and y offset to the view can be dragged across the screen (is this the correct way). There are several views on which the view can be dragged-on. See the screenshot below. What is the preferred way of detecting the target view the view is dropped on? I have included some sample code.

class MainActivity : AppCompatActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)

        var deleted by mutableStateOf(false)
        val x = mutableStateOf(0f)
        val y = mutableStateOf(0f)

        val colors = listOf(Color.Green, Color.Gray, Color.Blue)

        setContent {
            DragAndDropTestTheme {
                Surface(color = MaterialTheme.colors.background) {
                    Column() {
//                        This row contains potential drop targets
                        Row(
                            modifier = Modifier
                                .height(150.dp)
                                .fillMaxWidth()) {
                            colors.map {
                                Box(
                                    modifier = Modifier.background(it).weight(1f).fillMaxHeight()
                                )
                            }
                        }
                        Box(
                            modifier = Modifier.fillMaxWidth().fillMaxHeight()
                                .background(Color.Magenta)
                        ) {
                            if (!deleted) {
                                Box(
                                    modifier = Modifier
                                        .offsetPx(x, y)
                                        .background(Color.Cyan).width(75.dp).height(75.dp)
                                        .dragGestureFilter(object : DragObserver {
                                            override fun onDrag(dragDistance: Offset): Offset {
                                                val newY = y.value + dragDistance.y
                                                x.value = x.value + dragDistance.x
                                                y.value = newY
                                                return dragDistance
                                            }

                                            override fun onStop(velocity: Offset) {
                                                // Todo what is the best method of determining what box the component is dragged on
                                            }
                                        })
                                ) {
                                    Text(text = "Dragme", modifier = Modifier.align(Alignment.Center))
                                }
                            }
                        }
                    }
                }
            }
        }
    }
}

Hi everybody! I've been trying to wrap my head around compose and the way of creating UI in a declarative way by doing some of the code labs and trying to adapt a small app I have that makes a couple of API requests to an external API by using flow and Retrofit. Nevertheless I'm having some troubles observing the data in the ViewModel and just showing the results in a recycler view in the fragment. I haven't run into any example that does similar things, not even in the compose samples. Does anybody know any tutorial or repo that I can take a look at? Thanks a lot in advance!

How to make

Dialog

(not

AlertDialog

) full width?

Bothered by the fact that all @Compose UI components are in the Global namespace. As someone who does not start a project without DI and a clear Architecture this keeps bothering me. SwiftUI & Objective-C same issue How are people handling working in super large teams with name clashes ??? Wrap everything in a companion object just to get the namespace? Wondering if missing something ...