How can make Compose ignore pointer events and pass events to the elements below? I want top() not to consume any events

Box {
  content()
  top()
}

Hi, how to set click event as not consumed so that long pressing on it will repeat click action until release? As there is no boolean return for onLongPress in detectTapGestures.

Modifier.pointerInput(Unit) {
                detectTapGestures(
                    onPress = { onClick() },
                    onLongPress = { onClick() }
                )
            }

Hi Team what are the conditions on which we need to provide keys in LazyRow and LazyColumn , good article with example would suffice?

Hello everyone, I was unable to find a solution anywhere to my problem. My design has a number of screen where there are multiple lists (fully displayed, not scrollable lists) that are embedded within some kind of shared background, for example, a rounded box with a shadow. I am unable to use scrollable column, because it will throw an error due to unknown list sizes as they are dynamic. The only option I see is to use whole screen as a LazyColumn and wrap everything within item/items. The main problem is that I cannot put a custom designed background as "surface" and then use "items" keywoard to create a list inside. I had an idea to create background myself piece by piece, but I could not solve the shadow/elevation problem between each item. I attach code and screenshot. Any help is appreciated. Thanks!

Hey 👋 I have a ViewModel which has a

StateFlow<String>

. This flow is collected inside a Composable with

.collectAsState(Dispatchers.Main.immediate)

. The string inside is used as the value of a

BasicTextField

and the ViewModel has a function to update this value in the state. All goes as expected if the user is the one typing on the keyboard 👍 but, if a button is pressed on the interface, the value of the text field should be cleared a new value should be added as some kind of prefix (editable by the user, just as a helper). When I add this value in the ViewModel, the cursor of the text field stays at the beginning instead of moving to the end of the text. I have read this article: https://medium.com/androiddevelopers/effective-state-management-for-textfield-in-compose-d6e5b070fbe5. But I thought with

Dispatchers.Main.immediate

it should be all good? Thanks for the help.

Why doesn’t the inner box fill the outer box? Screenshot in thread

@Composable
private fun MyLayout(){
    Box(Modifier.fillMaxSize().background(Color.Yellow)){
        Box(modifier = Modifier
            .background(Color.DarkGray)
            .sizeIn(minWidth = 200.dp, minHeight = 200.dp)
        ) {
            Text("BOX", modifier = Modifier.align(Alignment.Center))
        }
    }
}

hello Everyone. i am working on compose ui and i want to check if app is installed in phone then open application otherwise redirect to the playstore. i am able to redirect the playstore but for me, app is installed in my phone and still redirect to the playstore. can someone help me on this, or whats am missing. #compose-android

val isAppInstalled = try {
    packageManager.getApplicationInfo(appPackageName, 0)
    true
} catch (e: PackageManager.NameNotFoundException) {
    false
}
if (isAppInstalled) {
    val launchIntent = packageManager.getLaunchIntentForPackage(appPackageName)
    startActivity(launchIntent)
} else {
    val playStoreIntent = Intent(
        Intent.ACTION_VIEW,
        Uri.parse(playStoreLink)
    )
    startActivity(playStoreIntent)
}

I'm trying to create a menu where you can drag from the red circle to the blue ones. I want to detect when the user is holding the finger over any of the blue items and also, when it releases, which one it was. Right now I've a

detectDragGestures

on the Red circle but I'm not sure I can detect when the blue one touched. I've tried

pointerInteropFilter

but it doesn't give me any events from the blue ones. Any suggestions? 🙂

Hey guys. how can I make scrollable the layout below? • ConstraintLayout ◦ Image ◦ Column ▪︎ ... I tried to use the verticalScroll modifier in the contraint layout, but only the image is being scrollable...

I am experiencing a strange memory leak with Compose with AnimatedNavHost from Accompanist and AndroidView. 1. Start from page A that contains an AndroidView 2. Navigate to page B (without popping page A) 3. (Page A is removed from the composition (onDispose called etc)) 4. Page B is popped off the stack, returning to A 5. Repeat indefinitely. Every time page A is displayed, a new View is created and the previous Views never get garbage collected. Any idea why this might be happening? Is it possible that a reference to the View could be accidentally stored somewhere or could this be a bug in Compose/Accompanist/Navigation? An additional possibly important detail: GC happens normally if A is popped off the navigation stack. EDIT: I managed to debug this and find the root cause. I will write an explanation in 🧵 later if anyone else experiences the same issue. Done.

I have a composable ‘screen’, that uses

LaunchedEffect

to perform one-off navigation events, based on state. So, for example, if the current

viewState

is

Unauthorized

, I might use a

LaunchedEffect

to call

navigateToLoginScreen()

But, let’s say there are two of these launched effects, with two possible navigation destinations. I’ve noticed an issue where, if the

viewState

updates and triggers a navigation event - the

viewState

can again update before that navigation transition is complete - triggering yet another navigation event. This means my navigation can end up in an unexpected state. Is there a way to ensure a LaunchedEffect is cancelled before the composition leaves the tree (like, during a navigation transition)?

Hello! How to specify width of TextField in character count?

What's the issue with passing a navigator into a composable or viewmodel?

motion layout for compose - • how can i set a box width to be 2/3 of screen and 16:9 ratio for height • set the 1/3 of the content with details and fill the max height

How to give this kind of Starting Border to a view in compose , the front Border height depends on the contents on the right?

Is there any schedule on when 1.4.0-rc02 or 1.4.0 is coming around for compose ui? I'm eagerly waiting for a bugfix that will hopefully be included there 😅

It seems to be possible to get the new focus modifiers in an inconsistent state and the app will crash on next key press:

java.lang.IllegalStateException: Event can't be processed because we do not have an active focus target.
    at androidx.compose.ui.focus.FocusOwnerImpl.dispatchKeyEvent-ZmokQxo(FocusOwnerImpl.kt:171)

EDIT: I have a hypothesis on why this is happening. I think it's a compose bug. Will write explanation in 🧵 EDIT 2: Debugged the root cause and created a minimal repro and recorded a demo of the crash

Suppose I have the following composable

@Composable
fun MySectionedLazyList(viewModel: SectionedListViewModel) {
    LazyColumn(modifier = Modifier.fillMaxSize()) {
        viewModel.section1?.let {
            items(items = it.items, key ={it.key}) {
                Item1(it.data)
            }
        }
        viewModel.section2?.let {
            items(items = it.items, key ={it.key}) {
                Item2(it.data)
            }
        }
        viewModel.section3?.let {
            items(items = it.items, key ={it.key}) {
                Item3(it.data)
            }
        }
    }
}

and I would like to scroll to the 5th item in

section3

, but I don’t know it’s index, only it’s key, how would I accomplish such a task? Everything I’m seeing requires use of the item index, which while I could compute, it would be much easier if there was a way to scroll to an item with a specific key rather than just based off index. Is this just functionality that I’d have to implement myself?

Are we able provide

WindowInsets

via a

CompositionLocal

?

I'm getting a

None of the following candidates is applicable because of receiver type mismatch

error in my Android Activity code, even though it builds and runs without issues. I've posted pictures of the exact errors below. These are my imports for those two functions:

import androidx.activity.compose.setContent
import androidx.activity.viewModels

These are my gradle imports:

implementation("androidx.appcompat:appcompat:1.6.1")
implementation("androidx.core:core-ktx:1.9.0")

// Lifecycle
implementation("androidx.lifecycle:lifecycle-viewmodel-ktx:2.5.1")

In a

LazyVerticalGrid

where the items are

2 x N

, is it possible for a given row to set both items to the max height of either row? My use case is that I have a tile where a title can wrap 1 or 2 rows. But I like the bottom divider and user image to be aligned at the bottom of the tile. I can’t set a fixed height because if both tiles have a title of 1 line or both have 2 lines, no adjustment is needed. Only when the left tile and right tile have a different number of lines, I would like to add a spacer or some way to push the divider + user image/details to the bottom

How can I pass data from Ascreen in Agraph to Bscreen in Bgragh in compose navigation???

any idea why this isn't showing in dark mode?

@Preview(uiMode = UI_MODE_NIGHT_YES)
@Composable
fun HelloWorldPreview() {
    MaterialTheme() { Surface { Text("Hello kotlinglang") } }
}

Using

ColumnScope.AnimatedVisibility

gives this annoying problem of having to do double check for the state, since the content lambda does not give the current state. Like:

AnimatedVisibility(model != null) {
  if (model != null) {
    ActualComposable(model)
    Spacer(Modifier.height(20.dp))
  }
}

Since I am not sure if doing

!!

in there is safe, as the old content may still be animating out, and it will call

!!

on the null item to try and render the item as it’s leaving. What do you folks usually do for this? Do I just have to do this double null check or is there something I can do instead, some API I may be missing?

With Compose 1.5.0 A1 I get the return of things like

java.lang.NoSuchMethodError: No static method AnimatedContent(Ljava/lang/Object;Landroidx/compose/ui/Modifier;Lkotlin/jvm/functions/Function1;Landroidx/compose/ui/Alignment;Lkotlin/jvm/functions/Function4;Landroidx/compose/runtime/Composer;II)V in class Landroidx/compose/animation/AnimatedContentKt; or its super classes (declaration of 'androidx.compose.animation.AnimatedContentKt'

Caused by libraires compiled with previous versions is there a way to workaround without forking those libraries?

Migrating from accompanist

FlowRow

to one in core Compose....this is what I had previously. From https://android-developers.googleblog.com/2023/03/whats-new-in-jetpack-compose-march-23-release.html, it seems equivalent is now

horizontalArrangement = Arrangement.spacedBy(8.dp)

but with that I'm not see any vertical spacing.

FlowRow(crossAxisSpacing = 8.dp) {
    session.tags.forEach { tag ->
        Chip(tag)
    }
}

Marquee is supported now????? 😮 I've been trying to come up with a way to do it properly and it's finally a real thing!

In case you haven't seen it. We released Compose 1.4 stable and Compose BOM March Release today. 🦜 https://android-developers.googleblog.com/2023/03/whats-new-in-jetpack-compose-march-23-release.html

Why is

resources()

marked as internal in androidx.compose.ui.res ? I am in a place where I need to decide on a string to be used inside my ViewModel. As described here, I am only exposing the StringRes Int from there, and I need to then resolve that string inside my composable. Specifically, I am outside of a composable context since I am resolving it inside a lambda, so I can’t just use the

stringResource()

function which uses this function internally. So it turns out I need to do what

stringResource()

does interally myself, which is

LocalConfiguration.current
return LocalContext.current.resources

So that I make sure I read LocalConfig in order to make sure I do not grab stale data.

resources()

already exists and does this exact thing, but it’s marked as internal, shouldn’t that just be a public function?

Isn't touch still supported in UIKit interop in Compose Multiplatform? I add a Mapview to the view, but I find that I can't operate it with gestures. Have any of you encountered similar problems?