Is there already a way to scope view models by composable?

I'm getting a very weird exception in a custom

Layout

check(measureables.size == 3) { "layout algorithm relies on 3 items in layout" }
val placeables = measureables.map { it.measure(constrains) }
layout(width, height) {
  val topPlaceable = placeables[0]
  val zoomPlaceable = placeables[1]
  // VVVV crashes on the line below with 
  //   IndexOutOfBounds(index=10, size=3)
  val locationPlaceable = placeables[2]
}

Index out of bound with index

10

(sometimes

12

) which isn't anywhere in my code. Can this be due to some compose compiler plugin magic? 🤔

Today, I tried to test some code, and of course I regret it now 🙃. I'm struggling to understand what's the best way to remove

delay()

in a LaunchedEffect code in reply

Does anyone know how i can get a piece of code to trigger if the user goes to the notification shade, and then comes back to the application? It doesn’t look like the composable on screen goes through any sort of recomposition, so I can’t necessarily figure out when to trigger the code. My screen is a roadblock to have the user turn on the bluetooth service when it’s off. I want to check when they come back to the shade whether it’s been turned on or not.

I’m creating a composable that has clickable subcomponents. I want the root composable’s indicator to respond to the subcomponents’ interactions. This is what I have so far.

If I have a

BackHandler

and an

AlertDialog

, the BackHandler is not invoked on Back press. Is that expected?

I don't know how to describe my problem, but I try it: When my App opens, it checks for a new version and if there's no new version it continues with the main app which also gets some data from an api. Now this should be a pretty easy task and the things being downloaded are very small. But sometimes with my wifi (and worse with only mobile data). My app takes very long to load. I don't know whats causing this. I mean the rendering is independent of the network thing it should give me something but its just a white screen

Is Navigation-Compose support screen transition?

When using

enableComposeCompilerMetrics

, what does

runtime

mean? I didn't see it mentioned in the documentation I've read, only

stable

and

unstable

. For example:

runtime class State {
  stable val text: String
  runtime var CREATOR: Creator<State>
  <runtime stability> = Uncertain(Creator)
}

That's for this class declaration:

data class State(
    val text: String = "",
) : Parcelable {
    companion object
}

I'm aware that Materials textfields are somewhat large but this looks like I've enabled retiree mode somehow

How can I do if BottomNavigation has a common screen? • tab1: ScreenA -> ScreenB -> ScreenCommon • tab2: ScreenC -> ScreenD -> ScreenCommon

Can compose work with kotlin 1.6.21 ?

Can a custom applier run a compose node factory asynchronously? I’m asking because I want to write a custom one for Filament, but some of it may depend on resource loading. Or, would it be best to load x resource first, then run the compose node once readied?

Hi , What is the alternative of ScrollBar in compose. I have already tried Modifier.verticalScroll . Wanted to understand is there a way to acheive scrollview

Is there any API to manually ask a component to recompose? It’s

drawWithContent

Can I “ignore” some events based on position in

pointerInput

so the events are passed to underlying components? See image in 🧵

What’s the best way to avoid clicking two items at the same time and navigating to both at once with compose navigation?

Just published an article explaining a productivity hack that will save you tens of engineering hours when working with Jetpack Compose - https://www.jetpackcompose.app/articles/productivity-hack-to-save-tens-of-engineering-hours-when-working-with-Jetpack-Compose

Hello to everyone. I am making a barcode reader with Jetpack compose and zxing library. I just want to have the rectangle area analyzed. Anyone have an idea about this?

Hi everyone , I have a question about @Stable annotation. I have the following class model with a List as a field. List considers as unstable field (check it in the compose metrics), so if I change the list content the composable functions that use this model will be recomposed again? Should I wrap the list under MutableState object? Thanks

@Stable
class PhotoViewModelItem(
    val id: String?,
    val title: String?,
    val savedGalleries: List<String>?,
)

I am implementing a low version of the real-time blur effect and it works well in most cases? But currently, I’m having problems with the coordinates on the

Pager

, as shown in the video, when a page is moved to the edge of the screen the image cuts out, after troubleshooting this seems to be caused by

onGloballyPositioned

returning the coordinates of a second pager...

I am using mapbox Library in my jet pack project, I need use Fragment provided by this library, I tried but no luck , is there any way to use Fragment in jet pack compose

Hello, we have a state object

CommonInput

in viewModel, which gets posted to StateFlow and then converted into a

@Composable fun CommonInputDisplay

in our Composable screen.

CommonInput

has a

value

param that gets converted to

MutableState

and used in

TextField

as

value

. The problem is that once it has initialized, we can’t change

TextField

value

by modifying state object from ViewModel anymore. How can we initiate a recomposition with a new value from viewModel by modifying

CommonInput

?

Hello here! I'm working on the dropdown for my design system with jetpack compose but I don't have an elevation when I test it with Android API 22 but it works perfectly with recent versions. Any ideas why? 🤔

I'm trying to do custom layout inside a Button and it seems I lack some insight into a layout procedure.

Button(
  modifier = Modifier.widthIn(min = 365.dp), 
  onClick = {}
) {
  Layout({ Text("hello") }) { measureables, constraints ->
    println("$constraints")
  }
}

I thought that incoming

constraints

would have minWidth set to

365.dp

, but they are actually

minWidth=0, maxWidth=636.dp

which comes from

Button

parent. What is the correct way to layout button's content with respect to imposed min size on the button?

Quick question as a sanity check: Is it true that when using View(XML)-based navigation components, the multi-backstack navigation and state saving is enabled by default but when implementing navigation via compose, we need to specify it ourselves like in this example.

Is there a way for me to precisely identify what state change is triggering recomposition? I’m experiencing x3 recompositions for what I’m perceiving as a single state change, and I want to try to track down what states are instigating each composition.

Trying to debug this crash where none of my files are in the stacktrace (see thread)… The only hint is the presence

androidx.compose.ui.platform.AndroidUiDispatcher

. Does this maybe mean that the crash happens in a compose effect? Or any other implication that could help debugging?