Hey everybody! Any reason why this happen? Basically when using BottomAppBar or TopAppBar even if I specify background color seems like some kind of alpha is added and I dont know how can I remove that (image on the left). When replacing Topappbar with surface the color is actually the expected (image on the right).

So, if i have a ViewModel with a MutableState object, how can i get that tied to a SavedStateHandle? I was consdering manually doing this with a snapshotFlow and having the viewmodel start a coroutine to monitor it and write it to the savedStateHandle. But this seems like a ton of boilerplace for something that LiveData gets out of the box. See thread for code.

I’m making an app in compose - and the designs use these shadows in many places, where they surround the outside of the component and then fade. What is the best way to achieve this in Compose?

Does passing arguments with Compose Navigation have an effect on performance? I have quite a few Strings to pass, but I might be able to find a solution to avoid it if needed. If it has no effect on performance, I'll take the easy route (no pun intended). 🤔

Hey all, I am calling a composable with lazy column inside of another compsable (homescreen) and getting this error. The problem I am running into is that I can’t have a vertical scrollState with a lazy column? What would be this fix?

java.lang.IllegalStateException: Vertically scrollable component was measured with an infinity maximum height constraints, which is disallowed. One of the common reasons is nesting layouts like LazyColumn and Column(Modifier.verticalScroll()). If you want to add a header before the list of items please add a header as a separate item() before the main items() inside the LazyColumn scope. There are could be other reasons for this to happen: your ComposeView was added into a LinearLayout with some weight, you applied Modifier.wrapContentSize(unbounded = true) or wrote a custom layout. Please try to remove the source of infinite constraints in the hierarchy above the scrolling container.

how to put a LazyColumn inside Column(Modifier.verticalScroll())

Is it possible to keep X number of a route in back stack and pop the oldest one once it reaches the limit?

Hello everyone :android-wave: . I've been playing with

SwipeToDismiss

and

swipeable/draggable

and was wondering if there's a configuration I'm missing to completely disallow swiping in a certain direction? Currently I see we have in

swipeable

a resistanceConfig that you can define. This would make it hard to swipe on a certain side, but not impossible.

Weird question. Is

remember { ... }

equal to

remember(Unit) { ... }

? Or does the

Unit

key override the implicit key derived from call order? Am I just overthinking things?

What’s the difference between these two? androidx.compose.compiler:compiler androidx.compose:compose-compiler

what is the best way to display a pdf with jetpack compose ?

I need to build a LazyRow with each item width be a percentage of the parent. Something like: ItemWidth = parentWidth/x. How can i get access to parentWidth and try to accomplish this? Any advice

if i want to change some color based on list scrolling or not, is this the correct approach:

var isScrolling by remember {
        mutableStateOf(lazyListState.isScrollInProgress)
    }
    
    LaunchedEffect(key1 = lazyListState){
        snapshotFlow { lazyListState.isScrollInProgress }.collect {
            isScrolling = it
        }
    }

Hi there, here is my first real app with compose, glad to hear your feedback! https://github.com/Amrjyniat/FullMangement

Is there a blog/twitter/anything I can follow to see compose specific libraries/projects that the community has created? There’s a couple github projects that curate a list but they aren’t up to date and lack some cool projects.

This message was deleted.

is there any specific channel for compose code review?

Is there a way to remember things across configuration changes without AAC VM? My specific use case is that I am using a MediaPlayer inside a class that I am now `remember`ing that I would like to persist when the user selects dark mode for example. But putting that inside a rememberSaveable seems a bit tricky, since I can’t persist its internal state because rememberSaveable will try to re-create it even after process death. Is ViewModel my only solution here for this use case of “persist it across config changes, but not across process death”?

Hi, i am creating app in compose and designer give me UI with 4 tab and inside every tab in need to show list and it should be searchable with any of column, So my problem is there are around 500 record on every tab so whenever user click on tab api should get called and fetch data from server and always show first 10 record at a time and then add navigation like move to next page it should next record if he click on last page then it should move to last 10 record i Attached UI for reference Btw i am creatiing UI for tablet Thanks in advance for help

In our (compose for desktop based) project we're using a lot of

mutableStateOf()

and a background thread for potentially longer running tasks that deliver data and alter state variables. Naturally, sometimes buttons etc. also write to such state variables. Now we're wondering about thread safety and what kind of synchronization mechanisms we might need. I realize the state handling and snapshots do a lot of heavy lifting for us, but it would be really nice to read some documentation about that. I find next to nothing on that topic in the compose docs: https://developer.android.com/jetpack/compose/documentation We have found Zach's series "Compose state explained" https://dev.to/zachklipp/series/12895 and the articles there are very insightful. Still I'm wondering if there might be other "official" resources such as docs or references on those topics that we might have missed?

Is this a compose compiler bug? Using #compose-web, this inside a composable does the expected thing:

@Composable
fun ElementScope<HTMLElement>.BlockChildLink(
  span: BlockChildSpan,
  markDefs: List<MarkDef>,
  content: @Composable ElementScope<HTMLElement>.() -> Unit
) {
  val link = span.marks.linkOrNull(markDefs)
  if (link != null) {
    A(href = link.href) {
      content()
    }
  } else content()
}

but this always results in empty content if the link is null i.e. the

content()

to the right of the elvis operator is ignored:

@Composable
fun ElementScope<HTMLElement>.BlockChildLink(
  span: BlockChildSpan,
  markDefs: List<MarkDef>,
  content: @Composable ElementScope<HTMLElement>.() -> Unit
) {
  span.marks.linkOrNull(markDefs)?.let { link ->
    A(href = link.href) {
      content()
    }
  } ?: content()
}

is there a better way to do this? Some items are disabled so they wont need click:

.then(if (isEnabled) Modifier.clickable { onItemClicked(index) } else Modifier)

Regarding this comment, if this is something that is safe to do, could we get some explanation/details about it on the official documentation? I haven’t found anything on the official docs but it seems like it’s a pretty interesting difference that we can take advantage of if we’re compose-first Activities.

how can I make an activity scrollable in compose?

I have a problem i need an advice on. I used to have brand colors like R.brand.blue that had two variantes, for light and dark mode. The resource system resolved them. With compose, i create brand colors like

val MaterialTheme.brandColor: BrandColor
    @Composable
    @ReadOnlyComposable
    get() = LocalBrandColor.current

and injected into the theme with CompositionLocalProvider. So in a composable, i can do MaterialTheme.brandColor.blue and it will resolve for light and dark. My problem: I used to resolve this colors in the viewMode, like using R.brand.blue and it was fine. In compose, i cannot do that, because it required a composable context. What can i do ?

Got a small issue with TextField and keyboard overlap. When I click on TextField the content is properly moved above the keyboard. But if if I use imeAction = ImeAction.Next to move to that TextField the content is not moved and stay under the keyboard. Is there some trick to fix this ?

Hi everybody ! Given this

LazyColumn

, how can I know if an item has been Long-clicked, and its index ?

Hi all, I want to test that my composables look correct so I want to check colour, spacing, font size etc. I’ve seen some references in the compose source code to Screenshot tests that use AndroidXScreenshotTestRule. Can’t find much information on this though. Does anyone know anything about these tests, like what dependencies are needed and how to set them up?

Does anyone know how to tie together a Switch with a Text so that the switch announces the text as it’s focused. Best i can find is using the “contentDescription” semantic property on the switch, and that should announce it, but then the text will also get announced as it’s own thing.

This message was deleted.