are you using emojicompat?

Hi guys, does anyone knows a library called formbuilder on github? It's great and it works for validating fields. However there's a function called getdata that creates a data class according to the data field in the form and it crashes even with a simple form of one string text field.

Hello everyone, I have a question regarding

ModalBottomSheetLayout

with a nested

LazyColumn

. I followed the docs how to implement this, but as it turns out there is a strange behaviour randomly happening, which causes that the list cannot be scrolled down further and also the end of list animation is shown. Does anyone know what’s causing this?

Hi guys, Can someone help me on to autoscroll the column item. I have

Column

inside that there are few items. Some of the item are hidden and visible on some condition. There is one

Nested Column

which is adding item and auto scrolling which is done with the help of this post. Item adding will done through

Add Me

CTA. Main problem comes here, when I was added more than 10 item and then we click on

Show Banner

CTA,

AnimatedVisibility

condition will true and display the view and

Nested Column

will shifted the few items downward. I don't won't like this, instead I wan't to calculate the whole column height and always show the last item. Same as done through in the answer gif.

ok so I am using/modifying

.value

stuff inside a

when

, which yes is technically not inside a Composable, and I’m being allowed to do so, but there is a big warning about it of course how do I avoid that?

LazyRow(
    contentPadding = PaddingValues(16.dp)
) {
    items(
        items = listItems.value,
        key = { it.type },
        itemContent = { item ->
            val label = when (item) {
                is BrowseEventsFilter.PeriodFilter -> {
                    when {
                        item.period.value != Period.Any -> {
                            item.enabled.value = ChipStatus.ENABLED
                            stringResource(id = item.period.value.label())
                        }


...............etc

Hello everybody and a Happy New Year! Let’s say I have a multi-module / multi-feature Android application in Compose. In one of the features I want to place a composable above all other composables (full screen), but of course this composable is not the top most composable in the hierarchy. I could put this composable at the very beginning in my

main

module, but then I would have a tight coupling of main and the feature. Is this even possible, a composable some layers down in the hierarchy rendering above all other composables?

Is there any way to seperate Glance import and Compose import? I always need to select one of them when I code... I also make Widget so I use both of them.

I have another question... Today I applied detekt with Twitter compose rules. And It says Composable function that is content should have modifier param from Top Level. I don't get it. Why is that? The function is like

@Composable
fun MyView(){
    // fixed content.
}

Hello everyone, I was trying trying to group list of events by day and sort the events within that day and I ran into a problem when I try to group the events for a given day by event type and still sort the whole events for that given day by start time regardless of the game type. Open to any suggestions. Thanks.

I'm writing a custom view to be used inside

AndroidView

, but when I run my app, my custom view does not appear. I was thinking perhaps passing in null for the

root

paramater might be problematic for

LayoutInflater.from(context).finflate(R.layout.view_visualization, null, false)

. Normally, I would call

rootView

instead, but that just returns my custom view. Is there a way to instead have the root be the composable that calls this custom view?

How can I use vector drawable with the original

android:fillColor

in compose? `painterResource`seems to override these fillColor with Theme Colors.

Just a quick question on the @Immutable annotation. How should we treat things with immutable lists?

data class Foo(values: List<String>)

I have a

TextField

with validations, I want to show error(make

isError

property equals to true) only after losing the TextField's focus, not on the initial composition, how I can accomplish that?

Hi when I open my app from recents screen network calls work but I don't see updates on the screen. What could be the reason for that?

I would like to test for whether a lazycolumn (or any list) contains X items, not that X items are visible right now on the screen, but whether the list in general has this many items

This used to work but the

clickable

is not being applied anymore. What's the proper way to handle dynamic modifiers?

val localModifier = Modifier
    .fillMaxWidth()
    .height(IntrinsicSize.Max)
    .apply {
        if (!disableClick) {
            this.clickable {
                Timber.w("Music CLicked")
                onMusicClick.invoke(music)
            }
        }
    }
    .padding(8.dp)

I have a problem with

PullRefreshIndicator

; it stays stuck half-way down the screen and does not refresh anything. Here is my code: 🧵

Why does it matter if I call a composable from within a

when

in every branch, vs. producing a value with the

when

and calling the composable with the result? Former seems to lag the scrolling, while latter doesn’t

Code in thread`

I have a problem with the

PullRefreshIndicator

which stays stuck halfway down the screen and does not execute the function. Please see code in thread.

I’m trying to test a two finger gesture with the following code:

private fun SemanticsNodeInteraction
            .twoFingerGesture(offset1, offset2) {
        performTouchInput {
            down(0, offset1)
            down(1, offset2)

            up(0)
            up(1)
        }
    }

When I put logs in forEachGesture, it seems like the pointer id is set to 2 for all 4 events, and the event.changes size is always 1, instead of (1, 2, 2, 1) like when I do the same gesture manually. Is there something I’m doing wrong in my code?

Hello guys, There should be multiple screens in one screen. For example: in screen X, there will be screens A, B, C, D. But they all belong to X. Do I need to keep these screens as content or should I add them as navigation?

Hey there, Is there any way to pass on drag/touch event from one composable to another ? I have a button in my layout, so once i long press that button i show a popup....so if i long press a button and then drag my finger to the popup, the popup should continue handling the drag event. Is there any way to do this ?

Hi guys! Is there a way in Compose where I can detect if a text can actually fit and if not change the text to an abbreviation to make it fit?

I have a weird issue with recompositions. I have a function with the following metrics, but the function is never skipped even when the parameters don't change:

restartable skippable scheme("[androidx.compose.ui.UiComposable]") fun MenuButton(
  stable menuOpen: Boolean = @dynamic LiveLiterals$NavBarKt.Boolean$param-menuOpen$fun-MenuButton()
  stable setMenuOpen: Function1<Boolean, Unit>
  defaultFocusRequester: FocusRequester
  stable onWidthChange: Function1<Dp, Unit>
)

The problem goes away from defaultFocusRequested is removed from the parameters, so it's definitely related to that. The object that is passed is the same on every recomposition, but it never skips. Is there a bug in compose metrics reporting the function as skippable? 🤔

Does google have plans to publish a jetpack compose style CameraX implementation?

In the fragment world, we could have a shared top bar where each fragment could specify what gets displayed for the action items and receive the click events. In compose, the recommended approach seems to be to define the top bar outside the NavHost and use APIs such as

NavController.currentBackStackEntryAsState()

to mutate the top bar based on the current screen. This means the root Scaffold owns the declaration of the top bar. It works fine for simple cases like just toggling the visibility of the top bar or controlling the bottom bar, but I find it not very practical in the following aspects. I've searched around on this slack, but couldn't find an answer that feels satisfying.

Scaffolder(
    topBar = {
        if (current screen is "xyz") show this else that...
    },
    ...
) {
    NavHost {...}
}

1: How would the currently displayed composable screen receive the click event on the action items? Pushing the event down is discouraged. I found this post from Ian, but I don't get it 2: If which action items should display depends on the logic/data fetched from the current screen, how should that be communicated to the root Scaffold? 3: In reality with large apps, I would want to define/encapsulate such logic and click event handling closer to the actual feature rather than defining all variations of them at the root level.

I am using stateflow. One of the ui state is ErrorState. If api return error, it will emit ErrorState and as per it error message will display in ui. After error display, if i naviagate to other pages and navigate back ErrorState will again collect and error msg display. (Expected behavior as i am using stateflow). But i dont need to show error msg after naviagate back. I am thinking about certain solution like using another sharedflow for error state. Or if possible scoping viewmodel to composable so that new viewmodel instance created on naviagate back. Is there any other best recommend way to handle such type of issue.

As long as the screen for this composable is in the backstack the viewmodel will be kept alive. Once you pop the screen the viewmodel will be destroyed