Hi Community, is there a way build a button with cut out text, so I can see the background through the letters?

Based on Compose Compiler Metrics, it seems

Painter

and

Icon

are unstable and keeping the function as non-skippable. Any ideas how else I could optimize my Coil Image Grid? Or does coil already able to optimize this somehow. It’s quite slow

navigation argument

defaultValue

cannot be dynamic? I had the idea of generating an id by default to identify a particular nested navigation scope and share an instance of a class among them.

What version should

kotlinCompilerExtensionVersion

be targeting? I always thought it should be the compiler version, but on the docs it shows that it can be

1.3.0-alpha01

a version that right above doesn’t seem to come from the compiler dependency since it only has the 1.2.0 stable release. Am I misunderstanding something or is this a documentation bug?

Hello, is `TextButton`’s

contentPadding

depending on text length? Longer text lesser contentPadding or?

This message was deleted.

Hi!

Hi is it just me? or are Jetpack Compose "Out of the box" Dropdown menus "underwhelming"? shouldnt it be easier to add item dividers, ripple effect when items clicked, elevation changes etc or am i missing something? 🤔

I have a

LazyVerticalGrid

with a lot of boxes in it (containing images, it's a photo app). Each Box has a

Modifier.clickable { openElement(element) }

on it. If I remove this modifier my scroll speed is much faster. It seems to be a problem to create the lambda and modifier over and over again for each of the thousands of entries as a user scrolls by. Is there any way I can solve this in a away without creating a lambda for each entry?

EDIT: Hi everyone! I turn on the compiler flag for the compose metrics and I dont understand the following case- Why the VisibilityTrackerListener is unstable? is just an interface defines under module who run and compiled compose

restartable scheme("[androidx.compose.ui.UiComposable]") fun ShoppingCarouselCardItem(
  stable card: ShoppingCarouselViewItem
  stable index: Int
  onClickListener: OnClickEvent? = @static null
  unstable carouselVisibilityTrackerListener: VisibilityTrackerListener<BaseEntry>? = @static null
  unstable onCarouselHidden: MutableLiveData<OnCarouselHidden>

Has anyone tried to use K2 with Compose?

SelectionContainer seems to intercept all clicks. I'm trying to wrap ClickableText elements in a SelectionContainer. Any ideas? SelectionContainer seems to be very limited and all of the interesting stuff is internal.

Hi All, Would love to chat with people who have used compose to create an Android TV app? I know some of the latest dpad support items are still landing but would love to see where people have gotten to. We are running the latest compose version in our android tv app and still have some issues related to scrolling so would love to see how others worked around it? We are trying to avoid having to switch back to classic views for a chunk of the app.

*In Compose navigation h*ow can I go back to the previous destination without making it recompose? I have screen A which launches B, B pops up & provides some data back to A. When B goes to A again I don’t want A to be recomposed. Is it possible?

How can I do a screenshot of a full composable? If I do a

onRoot().capturetoImage()

the image won’t be larger than the size of the screen. I also tried wrapping it in a vertical scrollable column and then setting a test tag but the screenshot never gets larger than the screen size

Is there a branch where I can track the state of Compose FIR implementation?

I think I’ve hit a bug in Compose Material - is anyone else experiencing this? Basically

BottomSheetScaffold

is not rendering properly in Previews (only Preview as far as I can see) on

androidx.compose.material:material:1.2.0-beta03

but it does on the previous version -

androidx.compose.material:material:1.2.0-beta02

. More in 🧵

I am trying to create a list of items similar to a todo list with a checkbox and some text next to it. I also want to have a shadow item that the user can change focus to. Once they type into it, a new "data item" gets created. The problem I encounter is that my shadow item is different from the newly created item. Thus the focus is lost. I am not sure how to correctly implement this. I tried it with

key

and this does sadly not work. I think I know why (the item is not at the same "position" in the composable and thus can't be the same). Code in thread. Any help is appreciated!

Hello hello! With the new Compose library versioning schema, could I have Compose Compiler on

1.2.0

and the remaining libs on

1.0.5

.Or does this require a min version (I.E 1.1.0) to work? Cheers!

I'm trying to create a custom color scheme for Compose. According to the official docs it can be done like this:

@Immutable
data class CustomColors(
    val content: Color,
    val component: Color,
    val background: List<Color>
)

Then I'd use a

CompositionLocal

inside my custom theme to provide these colors. However, looking at different community samples I noticed that they do it like this:

class AppColors(
    primary: Color,
    secondary: Color
)
    var primary by mutableStateOf(primary)
        private set
    var secondary by mutableStateOf(secondary)
        private set

    fun copy(
        primary: Color = this.primary,
        secondary: Color = this.secondary
    ): AppColors = AppColors(
        primary,
        secondary
    )
    
    fun updateColorsFrom(other: AppColors) {
        primary = other.primary
        secondary = other.seconday
    }
}

Basically replicating the

MaterialTheme

Colors

class implementation. My question is which approach should I follow? I understand that by using

mutableStateOf()

I can guarantee that Composables will react to individual color updates, but what if I know that my color scheme will never change at runtime? Is that the only reason to use

mutableStateOf()

? Any thoughts on this will be appreciated

if I’d like to do something like this, this is a box with a surface inside and an icon inside the surface, sounds right?

Hello! I’m trying to help the compose compiler to mark the model as stable (because I have performance issue). So I have ImageDesctiptor - interface model that exists in module doesn’t run compose so I wrap the class in that way/ Where Im wrong?

@Immutable
data class ImmutableHolder<T>(val item: T)

and I see that metrics:
unstable class PhotoViewModelItem {
  unstable val imageDescriptor: ImmutableHolder<ImageDescriptor>?
  stable val isSaved: MutableState<Boolean>
  stable val photoType: PhotoType?
  stable val tagsCount: Int
  <runtime stability> = Unstable
}
========
runtime class ImmutableHolder {
  runtime val item: T
  <runtime stability> = Parameter(T)
}

Does anyone know if i can get a BottomSheetNavigator to allow me to default to something other than 50% height?

As I try to learn Compose, I find myself really struggling with what is Good(tm) in a compose universe, what is unacceptable, and what is just distasteful. Most of my Android experience is a couple years back, and I'm currently trying to port some BLE scanning code that has lots of references to Activities, and Intents, and RecyclerViews, but no ViewModels. So I end up having to ask myself "is there a better/newer way to do this, or is this a hold your nose moment." I am curious if anyone has any decent up to date good book recommendations? I've done a few of the official sanctioned tutorials, but I feel I'm still missing a lot of how to weave Composable functions (I get that part pretty clear) with the more stateful rest of an Android app.

If I have a separate file with my compose code, is there a way to access the android R.xxx.whatever ids?

R

seems to be available, but it doesn't recognize

.string

or

.drawable

outside of an Activity class.

How would I go about adding a badge to a

NavigationBarItem

of a Material 3 bottom navigation bar? My initial attempt was to just wrap it in a

Box

and overlay the badge, but it seems

NavigationBarItem

has to be placed directly in the

NavigationBar

, so I cannot do that.

I noticed that

IconButton

(on the screenshot it's inside a

Button

content slot) has "rounded" tap area. When rendered using Compose Desktop I can actually misclick with the mouse in the corner leading to the whole button being pressed while I'd like a "dropdown" area to react instead. Can I somehow make it to be square?

Hello, how do you keep state of bottom tabs? Whenever I switch back and forth between tabs, everything is recreated and recalled. Code and video in thread

This message was deleted.