I have Column that consists of Text (aligned to the top of the screen) Scrollable Text (placed between the top text and bottom button) Button (aligned to the bottom of the screen) What is the easiest way to implement this? If I just place it in a Column the scrollable text pushes the button below the visibility of the screen.

I have a Column with

verticalArrangement = Arrangement.SpaceBetween

and if it’s

Surface

parent defines

.fillMaxSize()

, the Column’s height is not respected. More in thread

What’s the correct way to update an AndroidView when the Theme/Configuration changes? The view doesn’t update when changing Light/Dark theme

is there any way to animate between two textstyles?

Testing - the official docs on compose recommend we run AndroidTest for our composables that run on a device. Also i have seen people mention robolectric in this channel to run a bunch of tests quickly. We have a lot of modules in our company and CI would not efficiently handle all of the tests to run often on PRs with many or any emulators. 1. should we use robolectric even if its not perfect? 2. is there movement on making official headless compose unit tests that dont need a physical device (outside of robolectric) to verify basic ui interactions or snapshots

Hello All, I am looking at Textfields and I dont see a way to set Overflow for Text. Is there a way we set overflow with type ellipse.

Hi all! I have full-screen BottomSheetScaffold content and I want to make it scrollable inside the bottom sheet. I’ve seen this custom implementation but is there any support from the framework itself?

Is it possible to overlap two elements in a Surface, and for them to both be centred? With my current code, one element pushes the other one to the top left. I was expecting both to be stacked in the centre... I know I can do that with a Box, but I have to use a Surface. More in thread.

Wouldn’t memory leak if Context is provided as CompositionLocal like LocalContext(activity context by owner.context)? CompositionLocal values store in SlotTable, I know that SlotTable is just a linear array. In the case of an activity context, entering the array is a potential memory leak. Let me know if I’m misunderstood.

Hi, if invalidation occurs, it is recorded in

invalidateStack

, and if this stack is not empty, it is popped from this stack and returned from

endRestartGroup()

. Recomposition is performed through the returned

RecomposeScope

. Right? However, if there is no invalidation during the composition process, null is returned, and if invalidation is requested later, how does

endRestartGroup()

detect this and recompose again? If look at the implementation of

endRestartGroup()

, there is no code to track invalidations. Only request pop once.

val scope = if (invalidateStack.isNotEmpty()) invalidateStack.pop() else null // RecomposeScopeImpl?

EDIT: I found some clues. Suspend until invalidation is added through

awaitWorkAvailable()

in

Recomposer.runRecomposeAndApplyChanges()

. If there is a waiting task(

hasSchedulingWork

), it immediately resumes

Continuation

and proceeds to recompose. Otherwise, it maintains the suspend state. The maintained suspend(

CancellableCoroutine

) is resumed when the operation is completed through the

effectJob

, but as I traced the places where the

effectJob

is used, there are only

rememberCoroutineScope()

and

LaunchedEffect

. Where will this suspend resume? I think it’s time to record invalidation, but it wasn’t. They are recorded regardless of

Job

.

Hi guys, So basically I have all my UI state encapsulated in a single data class and expose it to the composable UI via single state flow. If I want to modify the state I use

_state.value = _state.value.copy(...)

. Does something like this should be avoided or affecting performance?

Hey folks, is there any way to open full keyboard in landscape mode? like it used to prior-compose? because right now it opens the same in portrait/landscape mode

For what reason does snapshotFlow() mix the concept of state updates with the concept of equality? I can easily say snapshotFlow().distinctUntilChanged() if I really want to check equality, but in the present system I cannot easily observe state updates where the evaluation result does not change in terms of equality, e.g. with SnapshotStateList (would have to make explicit list copies). Seems poorly thought out.

Hi all. I'm trying to achieve this animation but running into an issue (as you can see) where the fabs flashes out-of-bounds. Full

@Composable

in the 🧵

Has anyone had any issues with composables being laid out in the incorrect positions (under extremely rare, but reproducible scenarios)? Issue & details in 🧵

Hi there, I'm struggling with a challenge. I have two text fields in a row. One one the right side and one on the left side. In best case the whole text of the right side is always shown and the text on the left side takes the rest of the space. If the right text is too long the left text should have a min width, so that at least some text with ellipses is shown. In my solution the right text takes the whole width and the left text is hidden. Even when I set the min width (I thought I set it). Any idea how to solve it?

Row(
        horizontalArrangement = Arrangement.SpaceBetween
    ) {
        Text(
            modifier = Modifier
                .weight(1f)
                .widthIn(min = 200.dp),
            textAlign = TextAlign.Start,
            text = "Left side side side side side side side",
            maxLines = 1,
            overflow = TextOverflow.Ellipsis,
        )
        Text(
            textAlign = TextAlign.End,
            text = "Right right right right right right",
            maxLines = 1,
            overflow = TextOverflow.Ellipsis
        )
    }

In best case I would be able to tell the right text to take only 60% but if the 60% is not required take less. With

weight(0.6f)

it's a fixed space of 60% even if it's not required

the state is not a SnapshotState , why whenever it changed the canvas can redraw?

val state = mutableListOf(0f)

@Preview
@Composable
fun test() {
    Box {
        Button(onClick = {
            state[0] += 100f
        }) {
            Text(" > ")
        }

        Canvas(Modifier.fillMaxSize()) {

            drawCircle(color = Color.Red, center = Offset(state[0], 500f), radius = 200f)
        }
    }
}

Hey everyone, I’ve built a Compose library for ExoPlayer media playbacks: https://github.com/fengdai/compose-media Is anyone interested in this? Any feedback is appreciated! 😄 Here is the screenshot of the sample, which demonstrates how the library’s

Media

composable reacts to parameters changes:

Recently I checked the nowinandroid project to follow the best practices, but its repoistry layer doesn't seem to have any content about network requests. Both room/datastore support Kotlin Flow, and it will be automatically updated in Flow after data manipulation. But what about okhttp/retrofit? If the user action is handled in the viewmodel, how can I inform the api layer to re-initiate the network request and return the new data in the flow? are there any examples

Can I store a lambda in a variable that generates a (possibly nested) view, and only invoke the lambda if a certain condition is met (i.e. only add the view to the hierarchy if a condition is met)?

I am working on a Composable that is essentially this: https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/35122[…]3/original/pHTRjVez4mINgemCp15Ws5OFNs3a-xBXjw.jpg?1620046726. Anyone have thoughts on the best way to achieve something similar? See my thoughts in 🧵

Every Layout composable emits a ReusableComposeNode. But what does Reusable mean here? Below is the code of ReusableComposeNode.

@Composable inline fun <T : Any, reified E : Applier<*>> ReusableComposeNode(
    noinline factory: () -> T,
    update: @DisallowComposableCalls Updater<T>.() -> Unit
) {
    if (currentComposer.applier !is E) invalidApplier()
    currentComposer.startReusableNode()
    if (currentComposer.inserting) {
        currentComposer.createNode { factory() }
    } else {
        currentComposer.useNode()
    }
    currentComposer.disableReusing()
    Updater<T>(currentComposer).update()
    currentComposer.enableReusing()
    currentComposer.endNode()
}

I noticed with this code that the only difference between ReusableComposeNode and ComposeNode is the way the groups are created. The KDoc of startReusableNode(), which is the group creation method used in ReusableComposeNode, is written as follows.

Start a group that tracks a the code that will create or update a node

that is generated as part of the tree implied by the composition. A

reusable node can be reused in a reusable group even if the group key

is changed.

I don’t know what reused means here. Does this mean that the node is reused as measured? (normal nodes will start with the measure phase. but does the reused node skip the measured phase?)

What happens, when you don't use "key" in "LazyColumn"? Will the hash of the item be used instead?

Is Compose only working on specific Kotlin versions? I cannot seem to update past Kotlin 1.6.10, because then Compose complains.

Long shot, but after updating (Compose Compiler

1.1.0-beta03

, Kotlin

1.5.31

) to (Compose Compiler

1.1.0-beta04

, Kotlin

1.6.0

) I am having a weird issue where after navigating back to a Fragment the Fragment's UI (View-based, not Compose) is no longer responsive. Single-activity app with navigation component, issue appears with any View-based Fragment after navigating back to it (fine on Compose Fragments). I am having a hard time debugging this, or seeing why would updating the Compose Compiler affect non-Compose Fragments, did anyone see a similar issue?

A while back “Common tests” was moved from Backlog to “in focus” in the compose roadmap, are there any news on the progress on this? Its a pretty hard topic to search for 😅

Anyone familiar with MapView + AndroidView. I just have a simple map, and I hit a network call to get the lat + long of 5 places. When the network call returns I add those 5 items to a

var list = mutableStateListOf<Location>()

but my map never updates until I reload that page. I believe I'm doing everything correclty, because if I comment out my MapView code and replace it with a Column + forEach then all of my items show when the network call completes. Is there some sort of thing you need to hook into with AndroidView + mapView to have it respond to mutableState?

Hello Composers! Is there any straightforward way to directly handle software keyboard input without using

TextField

? Or more specifically: what is the most reasonable way to create a PIN code input widget with input from software keyboard? I'm used to hacks with invisible

EditTexts

in View system, but I'd like very much to avoid this stuff in Compose and do it the right way. Any recommendations?

Anyone else has a worse performance using Grid Layouts in compose compared to the old View System? I know the common solution is to use R8 and using the release build apk. I mean yes it is much better but not as good as the old view System. Especially when you use 4-5 Columns.