Hello 👋 Is there a runtime layout inspector for Compose ? I’m using

onRoot().printToLog()

for tests, but I can’t find the equivalent for a running app.

Hi everyone, does anybody knew how to set gravity or align text to

end

? basically, cursor starts from the right using

BaseTextField

Has anyone used 9patch images with compose? Can’t wrap my head around how to make it work. How can I set a 9patch as a background of, say, a

Box

?

What am I missing here? I want the red box to fill the space between the parent top and the top of the green box, but it ends up aligned to the centre of the green box.

ConstraintLayout(Modifier.fillMaxSize()) {
  val (box1, box2) = createRefs()
  Box(Modifier.constrainAs(box1){
    top.linkTo(parent.top); bottom.linkTo(box2.top)
  }.background(Color.Red).fillMaxSize())
  Box(Modifier.constrainAs(box2){
   bottom.linkTo(parent.bottom); centerHorizontallyTo(parent)
  }.size(200.dp,50.dp).background(Color.Green))
}

Hey everyone, what’s the best way to have sizes in our theme? So that I can access it like

MaterialTheme.sizes.medium

And we can specify sizes like small, medium, large (similar to shapes).

Can I change the constrains of a component inside a

ConstraintLayout

in base of a

mutableStateOf<Boolean>

? If the mutable value change, my component will have others constrains..

Following the Codelab about state / Step 6 / TodoItemInput https://developer.android.com/codelabs/jetpack-compose-state#5 As soon as i paste this code from the lab

@Composable
fun TodoItemInput(onItemComplete: (TodoItem) -> Unit) {
   // onItemComplete is an event will fire when an item is completed by the user
   Column {
       Row(Modifier
           .padding(horizontal = 16.dp)
           .padding(top = 16.dp)
       ) {
           TodoInputTextField(Modifier
               .weight(1f)
               .padding(end = 8.dp)
           )
           TodoEditButton(
               onClick = { /* todo */ },
               text = "Add",
               modifier = Modifier.align(Alignment.CenterVertically)
           )
       }
   }
}

my app does not compile anymore

w: ATTENTION!
This build uses unsafe internal compiler arguments:

-XXLanguage:+NonParenthesizedAnnotationsOnFunctionalTypes

This mode is not recommended for production use,
as no stability/compatibility guarantees are given on
compiler or generated code. Use it at your own risk!

e: warnings found and -Werror specified
w: /Users/adrian/Workspace/Android/android-compose-codelabs-main/StateCodelab/start/src/main/java/com/codelabs/state/todo/TodoScreen.kt: (84, 19): Parameter 'onItemComplete' is never used

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':start:compileDebugKotlin'.
> Compilation error. See log for more details

Hello! The latest Jetpack Compose minor release, alpha05, is here! You can get it now on Google’s Maven Repository. Release notes are available at https://developer.android.com/jetpack/androidx/versions/all-channel. As always, feedback is welcome; please log issues at https://issuetracker.google.com/issues/new?component=612128.

I have a question surrounding the

TextField

and related components. I couldn't find a way to filter between an onFocus/blur event vs actual typing/keyboard actions. The

onValueChange

handler is firing when I click in and out of the TextField and causes some un-wanted side effects. Am I missing something or is there currently a way (or a way around) to only account for keyboard actions and ignore focus/blur actions?

How can I have getQuantityString for plurals in Compose ?

All samples and codelabs have been migrated already to 

alpha05

 😄 Happy Composing! For the lazy: https://goo.gle/compose-samples https://goo.gle/compose-pathway

What's the deal with Compose components having this purple background? Did they purposely make the default theme obnoxious so you define your own? Is it too much to ask that they just look like the regular material design...

I wonder how does compose UI toolkit works internally? Does it have something similar to Flutter RenderObject tree, heavy UI objects which are reused?

So in the latest release,

launchInComposition

got renamed to

LaunchedTask

. Eerily close to

AsyncTask

in name and functionally (not entirely true) 😆

Hi, I am trying to use 

ConstraintLayout

  but i am not able to get the constraints to work properly.

ConstraintLayout(modifier = Modifier.padding(top = 16.dp, bottom = 16.dp)) {
        val (profileImage, progressText1) = createRefs()

        Image(
                modifier = Modifier
                        .constrainAs(profileImage){
                            start.linkTo(parent.start, 16.dp)
                        }.preferredWidth(72.dp)
                        .preferredHeight(72.dp)
                        .background(Color.Green),
                asset = imageResource(R.drawable.unknown_profile_empty)
        )

        val half = createGuidelineFromTop(0.5f)

        Text(text = "Sample text", modifier = Modifier.background(Color.Red).constrainAs(progressText1) {
            bottom.linkTo(half, 0.dp)
            start.linkTo(profileImage.end, 0.dp)
            end.linkTo(parent.end, 16.dp)
        })
    }

I am expecting that the text will align itself to the image end but it is not aligned to that

Column(
    Modifier.wrapContentHeight().aspectRatio(1f)
) {
    Icon(asset, Modifier.size(24.dp))
    Text("Action")
}

We expected this to be a square component; Why is Column expanding to the size of its parent? We figured to just use a fixed size to simplify things, I’m just curious why this wasn’t working. And I’m looking to know a solution for this in case we really need more dynamic sizing.

How do we display strikethrough and bold text in Text component? I tried SpannableString and Html tags string but it does not seem to work.

I'm aware of going stable next year, but is there a roadmap to help me decide when to start using it in prod before that?

What are your thoughts on using compose in prod? 💚 I'm already using 💙 it's ready for prod, planning to do so soon 🧡 planning for this year ❤️ planning for beginning of next year vote with reactions (I added 1 vote for each to make it easier)

Hi. I'm using liveData in compose and use

observeAsState

It is very odd that after update liveData compose ui update is not happening, but on some events ( click on items) I can see that model is updated! Is it better way to have handle items state outside compose? Thanks

Trying to annotate with data classes with

@Immutable

and read this bit:

data

 classes that only contain 

val

 properties that do not have custom getters can safely be marked as Immutable if the types of properties are either primitive types or also Immutable:

And then looked at compose-samples

@Immutable
data class Episode(
    @PrimaryKey @ColumnInfo(name = "uri") val uri: String,
    @ColumnInfo(name = "podcast_uri") val podcastUri: String,
    @ColumnInfo(name = "title") val title: String,
    @ColumnInfo(name = "subtitle") val subtitle: String? = null,
    @ColumnInfo(name = "summary") val summary: String? = null,
    @ColumnInfo(name = "author") val author: String? = null,
    @ColumnInfo(name = "published") val published: OffsetDateTime,
    @ColumnInfo(name = "duration") val duration: Duration? = null
)

I have data classes with

Date

. Anyway it should still be safe to annotate as long as I’m sure it doesn’t get changed right? Also, I have states with single-time events:

data class Event<out T>(val content: T) {
    var consumed: Boolean = false
        private set

    fun consume(): T? =
        if (consumed) {
            null
        } else {
            consumed = true
            content
        }
}

I guess I can’t use `@Immutable`for such state classes…

I've just implemented Tetris using Jetpack Compose. Check it out! https://t.co/198aK53XLB https://twitter.com/devpopalay/status/1316789701508911105?s=19

what is the best practice regarding the

Component

to use to just represent the

background

? I understand the in MaterialTheme the

Surface

has a similar goal, but it takes by default the

surfaceColor

. In my case where I want the same practical use but so that the background color is always

backgroundColor

. From looking at usages, it seems only

Scaffold

actually uses this color, but internally still uses a

Surface

and changes the background color.

@Ian Lake is there any more PR related with Navigation Args missing or the next snapshot will have Nav Args available?

I wanted to create a selfcontained “show version” component, simplest case would be like this

@Composable
    fun versionText(){
        val versionName = packageManager.getPackageInfo(packageName, 0).versionName
        Text(text = versionName)
    }

either this is the completely wrong way to do something like this, or I need some way to know if this composable is currently running in a preview, since the preview engine will not really show anything here (I think it even crashes silently somewhere)

Hi ! Is there a way to apply a

LinearGradient

to a

Text()

composable ? I’ve looked a bit into the docs, but can only find usages of solid colors for text.

PSA for snapshot users: the main AndroidX build and the Compose build have recently been merged. This means that the

/ui/

part of your snapshot build URL should be removed and the URL should be in the format:

maven { url '<https://androidx.dev/snapshots/builds/[buildId]/artifacts/repository>' }

PSA for Navigation snapshot users: the Compose Navigation artifact group+name has been changed. It is now

androidx.navigation:navigation-compose:1.0.0-SNAPSHOT

(using build IDs of 6910220 or higher - make sure to switch to the new snapshot URL format ^). Working towards the first alpha 🙂

speaking of navigation, should something like this work?

@Composable
fun BasicNav() {
    var isLoggedIn by remember { mutableStateOf(false) }
    NavHost(startDestination = "Profile") {
        composable("Profile") { Profile(isLoggedIn) { isLoggedIn = !isLoggedIn } }
        composable("Dashboard") { Dashboard() }
        if (isLoggedIn) {
            composable("Scrollable") { Scrollable() }
        }
    }
}

(the lambda passed into

Profile()

) is just connected to a

Button

to toggle the logged in state