I want to run the code coming from onClick parameter as well as some local code as shown below. How should I do that?

fun doSomething(onClick: ()->Unit) {
  //doing something
  Text("some text", modifier =     Modifier.clickable(onClick = onClick + //something that I want to execute here which can't be sent in onClick param)
}

Is it possible to have like a Surface with border, that fades outwards. Smth like this:

Hi everyone! is it normal than when navigating between composables, say have a list/detail model, when i click back the list composable recomposes? as in I click an item on the list, go to the detail, I click the back arrow and the list recomposes. The reason i think this is happening is because the List compose fetches the items using the

produceState

delegate from the network and it's called every time I go back, is that the expected behavior or something I'm doing wrong?

How do I implement exo player in LazyColumn that only play currently visible video element? My current implementation play all videos simultaneously.

showLayoutBounds

is supported within compose but it is integrated deep inside the UI core. I wonder if it is possible to create something like this on my own without tampering with the core. For example, by some modifier which adds some behavior to all subsequent composables.

Hi! How do I stretch image to fill parent bound with accompanist coil? I’ve tried

scale(Scale.FILL)

but it didn’t work

Will the Compose release of today support KT 1.5.20?

(Code in the thread) What would be the best way to avoid re-composition in this case? or rather avoid pager restarts

val scale by animateFloatAsState(
    targetValue = when {
        badgeText.isNullOrBlank() -> 0f
        else -> 1f
    },
        animationSpec = spring(
        dampingRatio = Spring.DampingRatioMediumBouncy
    )
)

This makes my badge jump a bit with an animation when a new badge is shown on my icon. I also want to make it bounce a bit when it changes value (ex. badgeText "1" -> "2"), say bounce to 1.2f scale and than back to 1f. What's the best way to cause this nudge? I suppose I have to use a

LaunchEffect

but than I do not know how to nudge the scale value in an efficient way, thanks in advance for any answer

Hi guys, is there some commitment, when compose supports new Kotlin releases "by default"? At least on new patch- or even minor-level Kotlin releases? Currently the build fails because of those "we may do not support this Kotlin version. Fix it with the

suppress

compiler argument". Is there something in the pipeline? Or is compose, unfortunately, now 100% coupled to an specific Kotlin release and we have to wait for a new release of compose each time a new Kotlin version comes out?

can you help to get rid of this jitter? code in thread

Hi everyone! I am struggling with GoogleMaps and its snapshot functionality. In order to prepare a google map snapshot we should use the

liteMode

and SnapshotReadyCallback. With this code(code in thread), I am getting crash with error: Bitmap size needs to be more than 0. How can I set the initial size of the googleMap?

I want to load this chart into an

AppWidget

on Android. Compose doesn’t work in

AppWidgets

. I believe I saw someone on here mention being able to convert a

Composable

to an

ImageView

? Is that possible?

I want to show an error on a text field on AFTER a user has focussed on it and then left it. e.g. I click first name text input, and then click on last name text input, then first name text input should show red "First name required" The samples show how to have an error state, but it's based on validation of the input, not losing focus.

I noticed ,when writing in a

BasicTextField

, that pressing the Android back button triggers a “de-focus” of the textfield. This results in the user having to press back twice for backwards navigation: the first press is to de-focus the text field and the second is to actually navigate to the previous screen. Has anyone experienced this too? I assume this is by design, how to work around this (i.e. navigate back immediately without the de-focus first)?

Hi, Is there a way to show an

AlertDialog

with custom content? like I want to show a list of itms to select one (like old android AlertDialog.singleChoice())

Has anyone else noticed an their saved states increasing after converting to Compose? We recently started integrating Compose into our app, and the converted Fragment started triggering our checks preventing large saved state bundles (we used to have a problem with

TransactionTooLargeException

). Compose inflated our saved state by 3x for the Fragment! Kind of surprising given the functional, state-hoisting nature of Compose. I've done some investigating, and there is no smoking-gun culprit, just some inefficiencies (assuming their not required) that add up on complex screens. Findings in 🧵

question: Is it possible to avoid the soft keyboard (IME) covering an input

TextField

when opening? I've a big form with TextFields. When i click on one close to the bottom of the screen the IME open up and cover it is there a way to make the view scroll up just enough so that the TextField is visible? Is this supposed to happen or am I doing something wrong?

How can we integrate Youtube Data API in #compose? I have just integrated Google-Sign-In in my app, and now want to integrate YouTube-Data-API, I tried to follow this guide https://developers.google.com/youtube/v3/quickstart/android, but I don't know how to implement that into Compose.

👋 Compose beta09 thinks that my project is using kotlin 1.4.31 instead of 1.5.10. I suspect that this is because some dependencies are pulling in stdlib 1.4.31. Explicitly adding stdlib 1.5.10 as a dependency fixes this error. Is there a better way of solving this?

error: this version (1.0.0-beta09) of the Compose Compiler requires Kotlin version 1.5.10 but you appear to be using Kotlin version 1.4.31 which is not known to be compatible.  Please fix your configuration (or `suppressKotlinVersionCompatibilityCheck` but don't say I didn't warn you!).

I’ve already tried declaring

kotlinCompilerVersion

and

kotlinCompilerExtensionVersion

under

composeOptions

.

I have been really enjoying trying out Mosaic. I have been slowly introducing it into a bot I am making for a game. Super enjoyable so far. I would encourage anyone making a CLI / Bot to give it a go.

Any reason why there was no new Compose release today?

Feel like I'm missing something basic. Anyone know why this doesn't compile?

var myCount by remember { mutableStateOf(0) }
val shouldDisplay = remember { derivedStateOf { (myCount > 1) } }

Anyone know if there’s a decent equivalent of NumberPicker for compose? The normal android view is way out of date in terms of it’s support for theming, so using an AndroidView wouldn’t really help me. I don’t see any existing Composable that would implement this. I saw some gists on the web for one that scrolls through the numbers, but the non selected numbers are only visible while scrolling, and disappear when a number is actually selected. I’m looking for the style in the system NumberPicker (which also is used in DatePicker and TimePicker)

Hey, if anyone has a moment to take a look at this issue I’m having that would be wonderful. https://stackoverflow.com/questions/68187240/custom-layout-draws-position-0-off-screen-when-content-is-larger-than-screen Essentially when I try to place a placeable off screen, instead of position 0 drawing at position 0, it’s drawing as if the total content was centered, so the further i am off screen, the further x=0 gets drawn, such as -300 I feel like there is maybe a way to handle this with AlignmentLines but i can’t figure it out if so. Also, dividing the difference by two and tacking that on seemed to work for width, but it’s not working for height even if i try to account for the statusbar/toolbars etc, and it. seems pretty hacky anyway

Does this look super terrible and not idiomatic compose? All I want to do is create my own composable called

OutlinedTextFieldWithFocusLostError

I have this

var focusLostCount by remember { mutableStateOf(0) }
val shouldDisplayError by remember { derivedStateOf { (focusLostCount > 1) } }
OutlinedTextField( modifier = Modifier.fillMaxWidth(1f)
                  .onFocusChanged { focusState -> if (!focusState.isFocused) { focusLostCount++ } },

So basically I just want a quick solution on a user clicking on a text field, and then clicking away onto another text field, hence triggering shouldDisplayError which itself runs some validation to check if the input is empty. Having a counter seems a little fishy though, hence the question.

Hi guys, Is anyone done Flexbox layout in compose?

I found that Compose UI swallows error log(but still freezes) inside some places(which seems to be called from ui nodes?) for example inside

graphicsLayer { /* this lambda */ }

so far harder to debug. Why does this happen?

Does Paging 3 no longer returns the

null

value during loading data from network? version: 3.0.0, compose: 1.0.0-beta08