Does Compose provide a way to measure intrinsic text width/height, synchronously, offscreen OUTSIDE of @Composable function? I'm integrating with a legacy system and it requires measuring certain things ahead of time, with View's you can simply do:

val view = MyView(context)
view.measure(widthMeasureSpec, heightMeasureSpec)
return Pair(textView.measuredWidth, view.measuredHeight)

I guess I could use

ComposeView

for this but I'm wondering if there is something more directly available in Compose API.

I'm looking at the animation API and either I'm missing something (most likely) or it's harder to implement this using Compose. I want to implement a shake/wiggle animation. Imagine a

TextField

and a button. When the user clicks the button, if the value in the

TextField

is not correct or empty, I'd like to move the

TextField

to the left/right a few times to draw the user's attention. In a

View

world I can do something like this:

ObjectAnimator
  .ofFloat(myTextInput, "translationX", 0, 25, -25, 25, -25,15, -15, 6, -6, 0)
  .setDuration(duration)
  .start();

But with Compose I can't figure out a way to have the current and target value be the same. The direction I went into is to use

animateDpAsState

together with

keyframes

animation spec to animate the

offset

of my

TextField

and it does the job. My issue is how to trigger the animation.

Hi guys! I think that I'm having a race condition here with

ModalBottomSheetLayout

. Code in 🧵

Anyone lost Android Studio’s

Interactive Mode

on 4.2 Beta? I can’t seem find out why its missing?

Is this normal behavior? Why is refresh random? (Swipe Refresh & Paging)

Does anybody met next exception [thread] ? Why can it be? I have code with finite loops just for represent button styles from design system [thread]

Is kotlin.serialization compatible with compose? I get this: org.jetbrains.kotlin.backend.common.BackendException: Backend Internal error: Exception during code generation

I just published another post in (what is turning out to be) a series on Compose’s state management model. Feedback welcome! A historical introduction to the Compose reactive state model

Hi everyone, I was playing with the AnimatedVisibility() today, and wonder if there is a way to figure out when the animation end. Does anyone know something about this?

I saw this question here and makes me think: How’s

match_parent

in Compose? 🤔 https://stackoverflow.com/questions/67677125/fill-height-for-child-in-row

has anyone had experience of enabling list scrolling in compose using a rotary encoder (e.g. twisting a watch crown)? I’m starting to suspect it may not be supported.

A question: shouldn't the

State

interface have

out T

and not just

T

? Like

State<out T> { ... }

Hi guys, I'm trying to put the following jetpack-compose code in a separate gradle module called

ui_components

(android library)

/**
 * Display a vertical list of [OutlinedTextField]
 */
@Composable
fun Form(fields: List<FormField>) {
    LazyColumn(content = {
        items(fields) { item ->
            OutlinedTextField(
                value = item.mutableState.value,
                onValueChange = { item.mutableState.value = it },
                label = { Text(text = stringResource(id = item.label)) },
                isError = item.isError(item.mutableState.value)
            )
        }
    })
}

However, when I compile the logs show me the following error:

e: org.jetbrains.kotlin.codegen.CompilationException: Back-end (JVM) Internal error: Couldn't inline method call 'items' into
local final fun androidx.compose.foundation.lazy.LazyListScope.<anonymous>(): kotlin.Unit defined in com.xxx.xxx.ui_components.Form
{
        items(fields) { item ->
            OutlinedTextField(
                value = item.mutableState.value,
                onValueChange = { item.mutableState.value = it },
                label = { Text(text = stringResource(id = item.label)) },
                isError = item.isError(item.mutableState.value)
            )
        }
    }

Am I doing something wrong here? Because individually the module compile (so no dependency missing, I guess) and without the dependency to

ui_components

the app compiles. Would be great if you can explain me, thanks in advance! 🙏

Hey guys, question about handling one-off events in Compose. I normally would deal with this by using a

SingleLiveEvent

and observing changes in my

Fragment

. Now that I’m in Compose world, it seems that using a

SingleLiveEvent

isn’t something that’s supported. What are your recommendations for handling one-off events coming from the ViewModel like showing a Snackbar, navigation, etc? Sample code in the thread of what I’m doing now.

Please tell me what's wrong? Why not "People". Material+Icons

What's the point of remembering the graph in

NavHost

here? As far as I understand it makes it ignore any graph update. https://github.com/androidx/androidx/blob/androidx-main/navigation/navigation-compose/src/main/java/androidx/navigation/compose/NavHost.kt#L98

Can not launch test for Composable elements, that launches before. I don’t notice when this test became broken, maybe after compose version update (current is beta07)

Is there some documentation about the "cost" of adding wrappers to composable? For example in a Column I want to have a Text in the middle with weight to fit all the remaining space. Seems it's impossible to directly center vertically the text, and the simple solution is to wrap the Text in a Row. But since before Compose the rule was always to avoid adding nesting for things likes that, it sounds like bad when maybe it just have 0 impact and is actually the perfect solution.

Can someone help clarify the best practices on using hot flows within Compose? Almost everything I’ve found seems to specify recommendations for cold flows explicitly. This article describes the use of

flowWithLifecycle

, which looks like it was introduced in a newer version of lifecycle than I have installed. Is

flowWithLifecycle

the best way or can/should one still use

shareIn

or

stateIn

with a hot flow to control the collection behavior in a lifecycle-aware way?

Is there a way to get an overview of the CLs that are being merged to the compose repo? I’m a gerrit noob so I don’t really have a clue how to dig in from https://android-review.googlesource.com/

Anyone know ho to use a unicode character in Text field? Getting an illegal escape error using this:

Text(text = "\u202")

hi, im using 

Hilt

 , but when I use navigation to jump to another page, the 

viewModel

 I get from that page is not the same as the 

viewModel

 I get here

Anyone know how to convert a

Color

to a native color int?

Is it reasonable to have a

@Composable

function with return type? I am trying to evaluate the feasibility to write JVM unit tests for them:

@Composable
fun spanStyleRange(textAttribute: TextAttribute): AnnotatedString.Range<SpanStyle> {
    val spanStyle: SpanStyle = when (textAttribute.type) {
        TextAttributeType.HASHTAG ->
            SpanStyle(color = MaterialTheme.colors.primary, fontWeight = FontWeight.Bold)
        else -> SpanStyle()
    }
    return AnnotatedString.Range(
        item = spanStyle,
        start = textAttribute.start,
        end = textAttribute.start + textAttribute.length
    )
}

In thie example,

spanStyleRange

need to be annotated with

@Composable

because it is using

MaterialTheme.colors

I'm trying to figure out how to architecture some state. I have a screen that shows a book reader with a book, a current position, and a style. The problem is that I want to store (essentially) an integer page number in the db, but have a floating point page number to represent in-progress page terms in the view model. To do this I think I need to have the source of truth be the view model, which simultaneously updates the repo. In contrast, I want a standard flow for the style where I update it in the repo and then the change flows back down to the view model and then the view. I currently combine these pieces of state into a single flow in the view model, but the different sources of updates led me to some bugs. Is there a cleaner way to do this?

I have trouble grasping how recomposition works in example I currently have. Code and more info in thread.

Is there any plan for targeting Fuchsia? https://www.theverge.com/2021/5/25/22452620/google-fuchsia-os-nest-hub-smart-display-update-operating-system-linux-kernal

Are there any HTML renderers available in Compose?

Anyone else having issues with LazyColumn on Beta07? My items become invisible in a weird way after I updated to beta07. Based on my Git log it doesnt look like I have changed anything else that can have such effect.