Hi i am using the compose backdrop

BackdropScaffold

there are a number of features i do not like and would like to customise 1). when the back layer is open the user cannot interact with the frontlayer. is there any way i can enable frontlayer interactions while the backdrop is open? 2). i would like to animate the transition between Hamburger and Cross icon, however i cannot see how to achieve this. 3). I have added my own animation for conceal/reveal of the back layer which i like however it has made the transition between the hamburger and cross icon very "sluggish" what have i done wrong?

Say you have some (state) class

Foo

and you want to create a

@Composable fun

to build some UI for

Foo

instances. How would you name it? • `Foo`: note that this is the same name as the

Foo

class. This is not an error (if class and function are in different namespaces), but it could be confusing. •

FooView

•

FooComposable

Something else? Are there guidelines for composable naming?

Hi guys I want to implement swipe to delete in lazyColumn, is there any src code for this?

Hi is there anything official Documentation about notifications in Compose or a sample App for that?

Bunch of compose updates today! 😛arty-parrot: Compose supports kotlin 1.7.0 in compiler 1.2.0 https://twitter.com/JimSproch/status/1542193552326680577 (kinda weird I think for it to be in 1.2.0? maybe just me?) Version 1.2.0-rc03 out today • Pretty minor bump Version 1.3.0-alpha01 • New

LookaheadLayout

that supports a lookahead pass before the actual measure/layout. • Introduced the

UrlAnnotation

annotation type and associated methods to support

TalkBack

link support in `AnnotatedString`s. • Add optional alpha parameter to Brush flavor of

TextStyle

and

SpanStyle

to modify opacity of the whole

Text

• Added a new API

WindowInfo.keyboardModifiers

to observe its state within composable functions or via snapshotFlow Version 1.0.0-alpha14 • Nothing too major. See here if curious

I’m trying to record a RoboScript for an app built with compose and I get the error

espresso testing framework does not support compose projects

. When I Google this error, I only find articles about how to use espresso with a compose project. To my knowledge, espresso does currently support compose. I tried this on Chipmunk and Electric Eel. Has anyone run into this issue before?

Hello. I'm trying to implement accessibility requirements for a reusable component called

FullScreenLoading

. Requirements include to announce loading starting and finishing via TalkBack. I have two possible implementations using

DisposableEffect

in loading icon's composable scope and both are not ideal. Including code in comments. Any ideas to improve option 1 (from code) or maybe I should go with option 2 in cases like this?

My team and I don't always remember to size an image "correctly". With that I mean that the AsyncImage() (using Coil) doesn't have a defined size before it comes back from the network. Essentially we want to require a set size or a maxWidth with aspectRatio modifier. This helps us cut out Cumulative Layout Shift https://web.dev/cls/ (basically content shifting because an image loaded) We want to accomplist this by writing a lint rule (we're working on it) and potentially just enforcing to use OurImageComposable() that will wrap AsyncImage and itself it'll do some checks to make sure that the image bounds can actually be laid out fully without an image to come back from the network. How would you go about checking to make sure that the image has a deterministic height and width? My first attempt at this is basically removing the ability to set any modifier, and requiring that you either set a width + height with args and providing another version of the image that takes in args for fill width OR height + aspect ratio. Thoughts?

How to handle global ui element state and behavior?

Is there a way to add the compose plugin to a non-android module? We have issues with recompositions because of our kotlin domain module and its non-inferred stability of data classes.

I think this will get some hate from folks... but is it that bad to use snapshot state in an App level state holder instead of something like StateFlow? Example: Is this that bad? It's just so easy to use and I think the argument has been made before that snapshot state is a compose dependency, but it's not a compose UI dependency and so its similar to stateFlow in that respect.

@Singleton
class AppStateHolder() {
  var someBoolean by mutableStateOf(false)

Using a ComposeView

<androidx.compose.ui.platform.ComposeView
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_gravity="center_horizontal"/>

Inside of a

<LinearLayout>

and I am experiencing a problem where for 1 frame the ComposeView starts aligned to the left and then it jumps to the center. Is this something someone else has experienced as well? Any thoughts on a workaround aside from finally fixing that screen to not be so archaic 😅

Material3's newest Compose alpha includes a new List component. However, I cannot find the component in the official M3 documentation: https://developer.android.com/jetpack/androidx/releases/compose-material3#1.0.0-alpha14 https://m3.material.io/ Is it somehow possible to specify what documentation version I want to look at? The doc link https://developer.android.com/reference/kotlin/androidx/compose/material3/package-summary does not allow me to select the newest alpha version.

Is it better to store individual class properties as MutableState or the whole class? (Example of what I mean in 🧵)

I can’t find a way to constraint composable to grab all width but not more that N.dp. How do I do it?

Is there a way to recycle a compose ImageBitmap? I’m using multiplatform.

Is there a way with a Compose or a native / Skia canvas to apply Skia ImageFilters?

[SOLVED]

unselectedContentColor

of

Tab

is not respected. Do I miss something or is this a bug?

Tab(
                    selected = true,
                    text = { Text(stringResource(section.stringRes)) },
                    onClick = { selectedTabIndex = i },
                    selectedContentColor = LightGreen600,
                    unselectedContentColor = Color.Red
                )

Which should I prefer for creating item of Paging’s LoadState?

LazyColumn {
    ...
    if (lazyItems.loadState.append is LoadState.Loading) {
        item(contentType = Loading) {
            PagingLoadingItem()
        }
    }
    if (lazyItems.loadState.append is LoadState.Error) {
        item(contentType = Error) {
            PagingErrorItem {
                lazyItems.retry()
            }
        }
    }
    if (lazyItems.loadState.append.endOfPaginationReached) {
        item(contentType = EndReached) {
            PagingEndItem()
        }
    }

Or:

LazyColumn {
    ...
    item(contentType = LoadStateIndicator) {
        if (lazyItems.loadState.append is LoadState.Loading) {
            PagingLoadingItem()
        }
        if (lazyItems.loadState.append is LoadState.Error) {
            PagingErrorItem {
                lazyItems.retry()
            }
        }
        if (lazyItems.loadState.append.endOfPaginationReached) {
            PagingEndItem()
        }
    }
}

To reduce GC I want to have a static instance of

Modifier.weight(1.0f)

I have this extension function:

@Composable
fun ColumnScope.FillSpacer(): Unit = Spacer(Modifier.weight(1.0f))

Now I try to figure out how I can define my

val

for that. I find it a bit tricky because of the ColumnScope.

I'm looking to for weight() + with minHeight to force the column to scroll. Here is a question with solution but I'm not much satisfied with BoxWithConstraints solution. Is there any other option?

Column(modifier = Modifier.verticalScroll(rememberScrollState()).fillMaxSize) {
    Box(modifier = Modifier.weight(1f).sizeIn(minHeight = 160.dp))
    Box(modifier = Modifier.height(600.dp))
}

Why is compose compiler at

1.2.0

while everything else is at rc03? Is it because it is a classpath dependency? https://maven.google.com/web/index.html?q=compose#androidx.compose.compiler:compiler:1.2.0

Can we scope a viewmodel to a particular composable?

Hey all is there any way for a

Box

to stop constraining its children? I just want them to overflow when I

offset(x,y)

them or size them

Box(Modifier.size(256.dp)) {
    Box(Modifier.border(2.dp, Color.Red).size(512.dp)) {
    }
}

The inner box always gets constrained to the outer box which I don’t want, but I do want all the cool things about the box such as

Alignment

I just don’t want it to constrain children size, any ideas? 🙂

Is there a way to leverage

remember

in combination with Proto DataStores? I've defined my

DataStore

:

val Context.dataStore: DataStore<AppPreferences> = dataStore(serializer = ..., ...)

However, I would like to have a way to fetch single values inside composables:

@Composable
fun SomeUI() {
    val context = LocalContext.current
    var userFontSize by remembe { context.dataStore.data.fontSize } // or something similar

    // Re-composition happens if the value changes for some reason. And it also gets stored if the var changes.
}

It's easy to do with a

SharedPreferences

-backed

DataStore

since I can use keys to fetch the value and set it. But I am not sure how to do it with Protobufs.

What does the error

Something went wrong while getting root views
    java.lang.IllegalArgumentException: Failed requirement.

imply? I’m using an

AndroidView

composable in which I create an instance of a custom view from 3rd party library. The error happens when I quickly navigate to/from that

AndroidView

composable.

Is there a way to write hybrid UI tests with compose? I have a flow that I would like to test and on some places compose is used and on other places I still use xmls

Anyone have any suggestiosn on how to write a good test for using AlertDialog? I’m getting this as the second root in the tree:

Node #5 at (l=0.0, t=0.0, r=320.0, b=174.0)px
[IsDialog]
 |-Node #6 at (l=0.0, t=0.0, r=320.0, b=174.0)px, Tag: 'alertDialog'
    |-Node #8 at (l=24.0, t=8.0, r=45.0, b=49.0)px
    | Text = '[Let's try that again]'
    | Actions = [GetTextLayoutResult]
    |-Node #9 at (l=24.0, t=44.0, r=72.0, b=85.0)px
    | Text = '[Sorry, we ran into a problem. Please try again.]'
    | Actions = [GetTextLayoutResult]
    |-Node #10 at (l=176.0, t=115.0, r=240.0, b=172.0)px
    | Role = 'Button'
    | Focused = 'false'
    | Text = '[Exit setup]'
    | Actions = [OnClick, GetTextLayoutResult]
    | MergeDescendants = 'true'
    |-Node #13 at (l=248.0, t=115.0, r=312.0, b=172.0)px
      Role = 'Button'
      Focused = 'false'
      Text = '[Try again]'
      Actions = [OnClick, GetTextLayoutResult]
      MergeDescendants = 'true'

The problem is if i match using

isDialog()

, there seems to be no decent way of checking all descendants, only direct children. So i had to add a test tag to the actual alert dialog, and then i can use

onChildren()

to find one that has the right text. The other issue is that there’s no semantics indicating which one is the title and which one is the body. Same issue with buttons as well. I do suppose I could add test tags to each node individually in my call to AlertDialog. What are others doing here?

Is there any option for

rememberAnimatedNavController

not to remember

navController

across process death?