Hi folks, there is any similar API to ComposeView but for Dialog? I want to start a Dialog in a "legacy xml ui" and in this Dialog I want to use Compose. The source for AlertDialog or Dialog depends on a Composable function scope.

is there a neater way to conditionally apply modifiers than

modifier = modifier
  .let { if(canBeExpanded) it.clickable { expanded = !expanded } else it }

Is anyone using dropdown menus in their android app? I've just added support for compose to

cascade

and would like people to try out its beta: https://github.com/saket/cascade/releases/tag/2.0.0-beta1

Still some (probably) undesired behaviour with

rememberSaveable

inside

movableContentOf

: Calling

recomposeScope.invalidate()

inside

movableContentOf

changes the

currentCompositeKeyHash

which breaks

rememberSaveable

I've found a couple of issues with

LazyRow

and

stickyHeader

. 1. If the header is vertically higher than the content the

LazyRow

change height when the sticky header item would scroll out of view. 2. if the

LazyRow

has

contentPadding

this is ignored for the

stickyHeader

, I would expect the sticky header to snap in a position that respect content paddding. are these 2 issues know? should I open 2 but reports? I assume these 2 issues translates equally with

LazyColumn

What is the preferred way to use Saver with “complex” object ?

data class Container(val name: String, val items: List<Item>)
data class Item(val id: Int)

I know how to create a Saver for each (an object, or a list), but I’m not sure how to handle object that contains a list

does anyone know of a good resource demonstrating compose for web (example sites to browse)?

what’s the way to limit no. of characters in

Text()

composable?

Another question about the new

SavedStateHandle.saveable

API, is there an equivalent to

val argArticleId = savedStateHandle.getStateFlow(ArticleArgKey, -1)

that return a State ? I tried with

.saveable(ArticleArgKey)

but it seems the return value is a Bundle instead of a Long... (in my case)

Sometimes

remember

saved state is lost after screen is turned off and on. 🧵

I had a question in regards to topAppBar not playing nicely with insets, and so we've been relegated to using accompanist insets-ui. I could have sworn someone posted the gerrit link or something to topAppBar getting this functionality out of the box, but now my search skills are failing me. Does anyone remember that by chance?

I wrote a small composable that makes handling "is this dialog visible?" pretty much seamlessly, without adding any extra overhead. Its very minimal, but I thought Id share it anyway; it has helped me tremendously! Code in thread 🧵

LazyPagingItems<Episodes>

How to use group by with LazyPagingItems? I want to implement a sticky header list here so i would need to convert this to Map<String,List<Episodes>> here. One way i can think of is using the itemSnapshot list, but not sure if it's a good practice. Any help is appreciated. Thanks.

Is there a way to implicity pass some data to parent composable without hoisting the state? I basically need to let the parent know if it contains a specific kind of optional child composable.

How can we display a custom small view like this over any composable without adding it to Root Composable and controlling it's visibility. The use case is like on any screen if any error occurs this should be displayed and this view (composable) should not be included in every composable. How to achieve this ?? Any help will e appreciated

For my work, I need to show a row of thumbnails from different parts of a video in the bottom of the screen instead of a Slider, similar to when you view a video in iOS’s photos app. Is there a Composable or Android view that will do this for me?

hey all - has anyone been having issues with the

androidx.startup

package in association with compose?

Hello, I'm trying to write an integration test for an Android application entirely written in Compose that has a single Activity and uses the Compose Navigation to change the screen content. I managed to properly interact and test the first screen that is shown by the navigation graph but, as soon as I navigate to a new destination, the test fails because it does not wait for the NavHost to load the new content. This is my current code for the test:

@RunWith(AndroidJUnit4::class)
class MainActivityTest {
    @get:Rule
    val composeTestRule = createAndroidComposeRule<MainActivity>()

    @Test
    fun appStartsWithoutCrashing() {
        composeTestRule.apply {
            // Check Switch
            onNodeWithTag(FirstScreen.CONSENT_SWITCH)
                .assertIsDisplayed()
                .assertIsOff()
                .performClick()
                .assertIsOn()

            // Click accept button
            onNodeWithTag(FirstScreen.ACCEPT_BUTTON)
                .assertIsDisplayed()
                .performClick()

            // Thread.sleep(500)

            // Check we are inside the second screen
            onNodeWithTag(SecondScreen.USERNAME_TEXT_FIELD)
                .assertIsDisplayed()
        }
    }
}

I'm sure that is a timing issue because if I add a

Thread.sleep(500)

before the

onNodeWithTag(SecondScreen.USERNAME_TEXT_FIELD).assertIsDisplayed()

, the test is successful. But I would like to avoid `Thread.sleep()`s in my code. Is there a better way to tell the

composeTestRule

to wait for the NavHost to load the new content before executing proceeding with the next assertion? PS I know that would be better to test the Composables in isolation, but I really need to simulate the user input on the App using Espresso and not only test the Composable behavior.

is it more idiomatic/preferred to expose a

mutableStateOf

or a

StateFlow

/

LiveData

property from a ViewModel?

This message was deleted.

Hi, I’m trying to write a list with

LazyColumn

, there is a

ConstraintLayout

in the top of it and other items list below the

ConstraintLayout

. It works well until I changed the compose version from

1.1.1

to

1.2.0-alpha08

, and now it crashed every single time when I scroll the

LazyColumn

.

Hello here! I have a question about the

text

property we can call inside the

semantics

callback. What is the difference between

text

and

contentDescription

and why we should use an

AnnotatedString

as value? 🤔 Thanks in advance!

🤔 Would you try this snippet and see what it prints? I think there's an unwanted behavior under the hood... 🐛🧵

hello! is there a way to render markdown in a compose's Text? Do we need a library?

2 weeks passed. Where is the next release which have to be fix for the last issue? https://issuetracker.google.com/issues/229752147

I am just trying to get an older Compose project built again but after some tool and library updates the build fails with

2 files found with path 'META-INF/kotlinx_coroutines_core.version'.
Adding a packagingOptions block may help, please refer to
<https://google.github.io/android-gradle-dsl/current/com.android.build.gradle.internal.dsl.PackagingOptions.html>
for more information

Besides the fact that the given link is wrong I am wondering what I shall do to get that working again. kotlinx_coroutines_core is used in a thousand places. How can I find the conflicting ones?

If this becomes mature enough, I'd love to see this work upstreamed 🤤🤩

var startBluetoothFlow by remember { mutableStateOf(false) }
    LaunchedEffect(key1 = true) {
        if (!host.bleManager.isReadyForScanning) {
            startBluetoothFlow = true
        }
    }

    if (startBluetoothFlow) {
        BluetoothController(
            permissionState = permissionState,
            bluetooth = host.bleManager,
            navHostController = navController,
        )
    }

The problem is that BluetoothController is getting evaluated multiple times

If I have an

Image

, without knowing it’s size, how could I center something on top of the image? I want the the

Image

size to dictate the size of the parent

Box

. How could I do this in compose?