I only saw examples with actual instrumented tests and Expresso

Is there a way to find a composable function that causing performance issue? I tried to use Macrobenchmark, but CPU profiler just provide the timing of recompose…

Good Morning "Composers" 😉 can anyone assist with my question currently open on SO? https://stackoverflow.com/questions/74372019/how-to-employ-backdropscaffoldstate-offset-correctly-to-offset-front-contentlaye

Can I safely ignore compiler plugin warning with :kotlinnew: Kotlin 1.7.21?

hello, maybe somebody have answer to this: Is it risky adding @Immutable to an existing data class because we start using it in Compose ?

It's okay to use a BottomSheetScaffold even though I will not use drawer, fab, and other parameters?

supposing I have this piece of Compose code

BrowseEventsHost(
    eventsState = eventsState,
    locationState = locationState,
    bottomSheetState = bottomSheetState,
    navController = navController,
    filters = filters,
    browseEventsCallbacks = object : IBrowseEventsCallbacks {
        override fun navigateBack() {
            onBackPressedDispatcher.onBackPressed()
        }

        override fun onEventClicked(event: Event) {
            browseEventsViewModel.logEventClicked(event)
            startActivity(eventIntentFactory.create(event.id))
        }

I would like to show a Composable inside onEventClicked, do I setContent again and inside it show it?

I can't figure out how to keep my Button from getting pushed off the screen when the Text in the same Row is too long (even though it has TextOverflow.Ellipsis)... I have a Spacer with weight(1.F) between them to push the button to the End, it works when the text is short... (see thread for code and screen shot)

I would like to increase the press area a lot on one of the buttons in my application. What would be the best way to do that, without increasing the look of the button itself, but still allow the button’s custom press animation to show?

How do I use

Modifier.imePadding()

with

Scaffold

? (Material3) If I use both the scaffold padding (

PaddingValues

) and

.imePadding()

in my screen the padding on the bottom is greater than it should be. If I do not use the scaffold bottom padding and only use

.imePadding()

the padding is correct when the ime is open but it is too little when it is close. What's the proper way to use these APIs? (btw why is

WindowsInsets

not named

LocalWindowsInsets

like other "Locals"?)

Hey peeps. Do you know if there is another library like this in compose?? https://github.com/AmrDeveloper/ReactButton. Thx in advance

Hey , Stuck on problem with ViewPager. Trying to create view like Reels (instagram/youtube/tiktok).

currentPage

is awful and get triggered way to often so I have made my own implementation. yet LaunchedEffect are called too often (not only when value is changed). I’m suspecting ViewPager issue in compose. Code in thread

Hi all - weird question. You know how you can consume a

Stateflow

as

State

with

collectAsState()

; but is there a way to do the exact opposite? i.e get a flow update whenever a

State

changes?

Upgrading to compose 1.3, none of our icon resources are being minified / discarded anymore. Not sure if anyone else noticed this?

With

m3.NavigationBar

Whats the right way to apply

windowInsetsPadding

to bottom

NavigationBar

? I'm doing this right now

NavigationBar(
  modifier = Modifier
    .windowInsetsPadding(WindowInsets.navigationBars),
) {
  pages.forEach { page ->
    NavigationBarItem(..)
  } 
}

It looks all wrong 🤔

This message was deleted.

Trying out the new compose BOM and I have a question. When a BOM is for say <5 libraries, it’s kinda easy to go through the release notes and check while updating if there’s anything to update with the new version. Compose BOM has 30 artifacts under itself though, meaning that when I am bumping it I can’t be sure I am taking care of everything I would if I did the bumps one by one. And I am not talking about breaking changes in the code, I understand that the version upgrades are backwards compatible for the most part, but it’s also for stuff like when a library upgrades, sometimes they may introduce a new API which I see in the change log and go ahead and learn about it and use it immediatelly. This is not going to be happening with the BOM. So a question, is there anywhere where for a specific BOM update I can also see a huge list of all the change logs for the versions that got updated? A list of all the changelists that look like this; Example of compose material 1.3

Version 1.3.0 October 24, 2022

Important changes since 1.2.0

Behavior breaking change
Maximum supported elevation in dialogs and popups has been reduced to 8dp.

API Changes
Add a Pull-To-Refresh component to Compose (I29168).
Change parameter name from values to value in RangeSlider (I3b79a).

Hey guys, can someone help me figure out why I'm getting this when I use compose compiler version 1.3.2 and kotlin 1.7.20 (I've seen this https://github.com/google/ksp/issues/1050 but that was with a beta version of 1.7.20):

e: java.lang.NoSuchMethodError: 'void org.jetbrains.kotlin.codegen.state.KotlinTypeMapper.<init>(org.jetbrains.kotlin.resolve.BindingContext, org.jetbrains.kotlin.codegen.ClassBuilderMode, java.lang.String, org.jetbrains.kotlin.config.LanguageVersionSettings, boolean, org.jetbrains.kotlin.codegen.state.IncompatibleClassTracker, org.jetbrains.kotlin.config.JvmTarget, boolean, kotlin.jvm.functions.Function1, kotlin.jvm.functions.Function1, int, kotlin.jvm.internal.DefaultConstructorMarker)'
        at com.google.devtools.ksp.processing.impl.ResolverImpl.<init>(ResolverImpl.kt:143)
        at com.google.devtools.ksp.AbstractKotlinSymbolProcessingExtension.doAnalysis(KotlinSymbolProcessingExtension.kt:188)

Adding

WindowCompat.setDecorFitsSystemWindows(window, false)

in latest compose version seems to add additional vertical padding to my screens. Anyone experienced same issue?

Hi, I am using a custom Horizontal Pager made with

Layout

with custom draggable and state handling. I am facing problem with Pager height. If I give specific height, then it works fine. But if I don’t give any height and use

Modifier.wrapContentHeight()

then Pager does not show up. The items may have different heights that is why wrapContentHeight is must. I have tried to debug it and found out that, when no height is given then Constraints in

Layout

have height set to zero hence placeables get zero height. Kindly help. Code attached in the thread.

Hello, I have a design question. We have an app where first the following pattern seem to work. But now, we have a lot of screens, not all of them uses scaffold stuff, and we are moving states from everywhere

Scaffold(/*...*/){
   NavGraph(/*...*/)
}

Shouldn't it be better if we face it with a different approach, something like:

NavGraph(/*...*/){
   composable(A){ Scaffold(...) }
   composable(B){ ModalBottomSheet(...) }
   ...
}

Also by using the previous approach, we shouldn't have to move the scaffold state from one place to other, and each screen will know its own traits.

Compose updates were released yesterday (which also coincides with Android Dev Summit part 2) 😛arty-parrot: Some updates that stood out to me! Version 1.3.1 stable Nothing too major there it seems except for some bug fixes. Version 1.4.0-alpha02 • Introduced parameter in Lazy APIs to compose and place out of viewport items (I69e89, b/172029355) • Added

minLines

parameter to the

BasicText

and

BasicTextField

. It allows to set the minimum height of these composables in terms of number of lines (I24294, b/122476634) • Added

minLines

parameter into material and material3 Text,

TextField

and

OutlinedTextField

which allows setting the minimum height of the component in terms of number of lines (I4af1d) • A bunch of "low level" compose-ui api changes. None of them make sense to me (as a user of compose ui) but might be worth checking out if you care about that sort of stuff Check out Android Dev Summit Part 2, Form Factors playlist with tons of GREAT compose content included (compose insets, compose navigation, small mention of compose for TV, etc) https://www.youtube.com/playlist?list=PLWz5rJ2EKKc9jBnpl83LH6oZc7nFIVSRq

Hi all! I have a list within a LazyColumn and I do not know how to scroll to an item of the inner list. Can someone help me? I add more details in the reply

How to make Text wrap like swiftUI. I have a bunch of test cases in the thread. Basically it seems like the rules if you have 2 Text next to each other. If one of the Text is short the other one can fill the available space. Then if both are long then both take 50%. 🧵

movableContentOf with subcomposeLayout not working in 1.3? I know there was an issue that it didn't keep remembered state in 1.2 to move between subcompose and not, but without that type of change it was working in 1.2 -- our usage now is crashing after upgrading to 1.3. Maybe similar to https://issuetracker.google.com/issues/258053979 but the callstack is completely different, and in our case there is just 1 arg (modifier) that we're passing right now...

Hello! 👋 I updated to compose 1.3.1 from 1.0.5 and suddenly my very basic signature component stopped working. It has to do with with

pointerInteropFilter

But not sure why, maybe someone has a few pointers. 🧵

Hi there does anyone know how to handle click on leading or trailing icon on text field compose

In the TextField composable code, I noticed it annotated the lambda for the decoration box with @Composable, however it works without it. Does the compiler do something different when it's there?