Hi, how would I use compose for a

DialogFragment

?

Hey all, how can I add space between inside of the topAppBar? Should look like the figma

What would be the idiomatic way to autoscroll a scrollable when it's parent container padding change?

Can you

remember {}

a when statement? I'm trying something like this

remember{
   when (someValue) {
       optionA -> {
           doSomething()

but I get an error of "remember calls must not return Unit"

I think compose icons package must be separate from material package. It’s strange to import material package when using material 3 components

Hi I have a strange behavior using

Sealed class

,

when

and

flow

with

LazyColumn

🧵

Hi all, what is the best way to host a composable child that has a navbar? should we have two

NavHost

?

Hey everyone. I am looking for recommendations for animations between separate Composables - animate something from one Composable to another (details in comments)

Hi! I have a Side Nav drawer that I'm implementing using

drawerContent

in the

Scaffold

of

BottomSheetScaffold

and the bottomsheet is always displayed at the bottom partially(acc. to the designs). My issue is that when I open Side Nav drawer the bottomsheet is covering some contents of the Nav drawer at the bottom. I am able to collapse the bottomsheet all the way to the bottom when Side Nav is opened by using

DisposableEffect

but is there any other way to achieve this without the brute force method?

if (drawerScaffoldState.drawerState.currentValue != DrawerValue.Closed) {
     DisposableEffect(Unit) {
         onDispose {
       // do soemthing
        }
      }
 }

Is Compose Function can’t take in Reified inline function? The below example compiles well but fail at runtime

This function has a reified type parameter and thus can only be inlined at compilation time, not called directly

@Composable
fun Launcher() {
    val context = LocalContext.current
    LazyColumn(modifier = Modifier.fillMaxWidth(),
        horizontalAlignment = Alignment.CenterHorizontally) {
        item {
            context.StartActivityButton<LaunchedEffectActivity>()
        }
    }
}

@Composable
private inline fun <reified T : Activity>Context.StartActivityButton() {
    Button(onClick = {
        startActivity(Intent(this, T::class.java))
    }) {
        Text(T::class.toString())
    }
}

More info here https://stackoverflow.com/q/70768211/3286489

Is it expected that a text field (BasicTextField) stops working (no keyboard, no focus) if the parent has

clickable(enabled=false, onClick=...)

? This used to work.

Is the SideEffect

deriveStateOf

not able to work together with

snapshotFlow

in aiding recomposition? Separate them out seems working, but not together. The code example in https://stackoverflow.com/q/70771821/3286489

Is anyone super familiar with hiltViewModel() and compose nav. Starting to go crazy on this error that it can't create a VM. Am I doing something obvioiusly wrong here?

bottomSheet(route = Screen.DebugBottomSheet.route) {
  DebugBottomSheet(previousScreenVM = hiltViewModel(remember { navController.previousBackStackEntry!! }))
}

my bottomsheet

@Composable
fun DebugBottomSheet(
    viewModel: DebugBottomSheetViewModel = hiltViewModel(),
    previousScreenVM: ViewModel,
) {}

Error:

java.lang.RuntimeException: Cannot create an instance of class androidx.lifecycle.ViewModel

Hi all, I have a ParentFragment with CollapsingToolbarLayout + ViewPager2, and 2 childFragments inside the viewPager: one with compose LazyColumn and another with recyclerView. The problem I am having is that collapsingToolbarLayout collapses as expected when scrolling the recyclerView, but doesn’t move when scrolling the LazyColumn. how can I solve this problem?

The Compose roadmap has "Support Async Drawing" and "Support multithreaded scheduler" in focus, though I haven't seen anything about these since Compose went stable. Does anyone have more info on if/when Compose is implementing more multithreading or other similar performance optimizations?

Hi all, what is the difference between

navController.popBackStack()

and

navController.navigateUp()

Hello. I am using the

Canvas

composable in my compose desktop app. I have found that the

Canvas.onDraw

method is called multiple times although the size of the canvas has not canged. This leads to jank since the drawing is quite intensive. Next to the canvas i have a couple of items that are clickable() so they show hoover feedback for the mouse cursor. Even just hoovering over these unrelated items triggers a redraw of the canvas. Is there a way to circumvent this redrawing?

anyone implemented, deep linking in compose, any example??

Does anyone know how to update a recyclerview that is inside a Compose AndroidView?

Lets say I want to design a top level pop-up, like an in-app notification that should show on top of every screen regardless where the current user is navigated. How would you design your composable? Is this something I want to setup when configuring the NavHost in the MainActivity? 🤔

If I am grabbing data from a network call in the viewmodel can I show the data on my preview?

If I bring up and then hide the soft-keyboard, it seems to swallow an extra back-press (even after being completely hidden). Anyone else seeing this? Im using androidx.activity.compose.BackHandler.

Hey guys, is it possible to animate between two different composables?

Is it possible to override ripple color for whole application in one place?

I’m working on accessibility for a custom checkbox component, trying to get the error state to read out correctly on a screen reader. Right now when the checkbox has an error, the error message is not being read by TalkBack. The code looks something like:

Box(
 modifier = modifier
   .triStateCheckbox(…)
   .requiredSize(…)
   .border(…)
   .background(…)
   .semantics {
     error("Error invalid input")
    }
) {
 MyIcon(
  contentDescription = null,
  modifier = Modifier.clearAndSetSemantics {}
 )
}

I set some breakpoints and

SemanticsPropertyReceiver.error

is being set correctly, but

setContentInvalid

 in 

AndroidComposeViewAccessibilityDelegateCompat

 is not. I tried removing the inner icon since it’s altering its semantics but that doesn’t seem to change anything. I’m trying to figure out if I am doing something wrong in using

.semantics

or if there might be bug here.

Hi, I've opened a change request to Compose in AOSP Gerrit. Should I add Code Owners myself, or does someone make the rounds for external changes?

Does it make sense to back a toggleable component (Switch/Checkbox) using a

StateFlow<Boolean>

? Even if there are many such components in a list? (dozens? hundreds?)

SideEffect{}

is triggered on a successful composition. Let's say all I'm doing is incrementing a variable in that block. What if I wanted to increment on every composition (successful and "failed"). Is there any sideEffect type block for that? Or would I just put that in my composable without any sideeffect-esque {} and that basically counts as failed + successful compositions?

I've read Zach K blog posts on the topic but I'm still encountering a situation that I can't seem to untangle. Essentially I have a list of items. This list is a mutableStateList. Every item could also have a single property that is also mutableState. When I update this item mutableState, I don't see the composable recompose. Can anyone spot any egregious issues here?

class ScreenViewState {
  val list = mutableStateListOf<Item>()

and my Item

class ConcreteType(override val type: String = "") : Item {
    var something by mutableStateOf("beep")

then in my VM I call

(myItem as ConcreteType).something = "boop"

My composable always beeps, but never boops.