How to achieve crossed line

Text()

in case when text could be any size (multiple lines too)?

drawLine(maxWidth, maxHeight)

won’t work for me, cause it increase

Box

with

Text

to full screen. Maybe possible to measure text and then drawLine?

before Compose I use to hide keyboard when user started scrolling so that they can see more rows of the recyclerView this was the code I was using.

recyclerView!!.setOnTouchListener { v, event ->
    val imm = requireActivity().getSystemService(Context.INPUT_METHOD_SERVICE) as InputMethodManager
    imm.hideSoftInputFromWindow(v.windowToken, 0)

    false
}

was it the preferred way to to this now with compose? I have already considered using isScrollInProgress of LazyListState but I think this may not be suitable for this use-case.

I have a multi-module project and I'm trying to add compose to one of the ui modules. I followed the guide here but I keep bumping into this error:

e: This version (1.0.0-beta07) of the Compose Compiler requires Kotlin version 1.4.32 but you appear to be using Kotlin version 1.5.21 which is not known to be compatible

I don't know where the

1.0.0-beta07

version comes from. As far as I can see, I defined everything to use

1.0.2

We have a crash where user copies a text from a

TextField

in our

compose

-based application, and Android crashes our app with a

SecurityException

because some other app doesn't have

READ_CLIPBOARD

permission. Stack trace has compose api inside. Can this somehow be disabled for

TextField

? Should I report a bug? Stacktrace in the thread.

We’ve been having issues with scrolling performance, mainly with nested lazycolumns - one of the suggested fixes is the following - does it work? Any other tricks? “Make sure in release variant minifyEnabled is set to true and the ProGuard file is proguard-android.txt instead of proguard-android-optimize.txt”

Is there a good introduction somewhere out there that explains how the compose compiler plugin works? I would be really interested in that.

Is it well known that with two function receivers with the same extended methods on

Modifier

your code won't compile? See 🧵.

:android-wave: Is there a way to remove the padding/extra height from a

TextButton

? I've tried setting

ContentPadding

to 0.dp and using

Modifier.heightIn(min = 0.dp

but neither work for my use case. I'm trying to make my TextButton be the same height as a

Text

I have in a Row. I would use Intrinsics.Min but it doesn't respect that.

❓ 🔴 🧪 Compose Testing : How do I test if the exception is thrown or not? See more details in the SO thread

❓ Common problem around keeping focused things visible here; I'm curious how people are solving it. Scenario: • Screen with a text field (inside a scrollable area with IME insets), soft keyboard is not yet showing • User taps on text field - so it gets focused and the soft keyboard shows. • Insets shrink down, but the text field gets obscured behind the keyboard 🤦. The scrollable viewport has been shrunk, but its scroll state does not adjust to maintain view of the focused element. • How do you make sure the field stays scrolled-to-visible? Solutions in 🧵 👉

From a performance perspective, how horrendous is it to have

Layout { }

invoked every frame? Especially with lots of temporary collections being created with lines like

val placeables = measurables.map { it.measure(constraints) }

How to show composable like

Box

for few seconds and make it disappears.

[SOLVED] Using

addPathNodes

addPath(
   pathData = addPathNodes(
                   "M5.778,8.81a0.6,0.6 0,0 0,0 -1.2v1.2z" +
                   ...
   ),
   ...
)

Anyone already try to convert vector

pathData

to

androidx.compose.ui.graphics.vector.ImageVector

?

I’m implementing Snapshot Testing with Compose, however, when I compare the bitmap from different APIs (28 and 30 for example), I get an error saying they don’t match. So, I checked what was different, and looks like it’s the background color. The first pixel (0,0) gives me a different color using depending on the emulator API version. Looks like it renders a grey gradient at the very top (API 28 #E0E0E0 and API 30 #E2E2E2). It is reproducible with the following code.

Box(Modifier.background(Color.White)) {
    Button(onClick = {}) {
        Text(text = "Label")
    }
}

I’m using the Snapshot code example from @ppvi.

yes that is totally normal, you'll get differences even between emulators running on different platforms

Is there any way to make each element in a row the height of the largest element? I have these two cards and they should have the same height. I've tried a lot with requireHeight(Intrinsics.Min) but couldn't find a solution

Hi, is there a way to load and draw an xml shape drawable into a Canvas?

Hello all, I’ve been working on new task manager app with jetpack compose app. I’m facing

huge performance issues

when I’m

navigating

from

all task composable

👉

add task composable

.

Add task composable

screen is having multiple

OutlineTextField

. Is there any workaround solution for this? Here’s the sample video 👇 . See more details in thread below.

Hi. Is it possible to use jetpack compose to build a a library of widgets for my company? We have various mobile apps (and web apps) that would benefit from a consistent set of widgets the designers have come up with. They would just need minor styling after to use the color palette of the app. Any issues preventing this?

Hey, is there a simpler way to use a composable for placeholder image while it's loading? I assume I would need to hold specific state for this?

Image(
                painter = rememberImagePainter(
                    data = url,
                    builder = {
                        placeholder(...) // <-- I want to have a composable placeholder instead
                        crossfade(true)
                    }
                ),

Is there a way for compose to read fonts from assets and not from res\fonts?

I need help in solving many-recompositions puzzle. Reading a

LazyList

state causes the endless recomposition loop, I can't fully understand why. Minimal sample is in the thread.

I also have a recomposition-related question: all of the samples and basically every code i know, uses the

kotlin.collections.List

interface to represent a list of data. However the

List

interface is not

@Stable

. My experience shows that if a composable function is called with the same

List

of strings, it will always recompose. Should we use another type to represent `List`s (and other collections) in compose? This could be also a broader question, since lots of built-in immutable types (like

LocalDateTime

) are not considered stable by the compose compiler. I added example code in 🧵

Regarding unbound ripple, is there a way to control which composable can be drawn over? In this simplified code snippet, the ripple from the Text overlaps the TextButton, but it looks weird since TextButton has a different background color

Hi. Is there a way to remove underline of the text (when writing) in BasicTextField? I tried this, but underline is still there:

BasicTextField(
                    singleLine = true,
                    value = text,
                    textStyle = LocalTextStyle.current.copy(textDecoration = TextDecoration.None),
                    readOnly = readOnly,
                    onValueChange = {
                        onValueChanged(it)
                    }
                )

`All deeply immutable types can safely be considered stable types.`What does this mean? A Kotlin data class with all

val

is considered stable by the compiler then ?

In the sample code linked below, why does the second card not show all of it's elements?

Is it ok to set state type as a lambda? (

MutableState<(() -> Unit)?>

) I've been thinking about doing some kind of "confirmation dialog decorator" (confirmation or other, e.g. "request pin") for some user actions. It would be used like

var confirmationDialog: (() -> Unit)? by remember {
    mutableStateOf(null)
}

if (confirmationDialog != null) {

    Dialog(onOk = {
        confirmationDialog?.invoke()
        confirmationDialog = null
    }, onCancel = {
        confirmationDialog = null
    })
}

SaveButton(
  onClick = requireConfirmation { theRealSave() }
)

Is it too hacky? Any issue other issue?

I've been playing with the latest versions of the compose navigation, with accompanist animations, and I have one strange transition that's happening that I can't explain which seems to transition into the top left corner of the screen, and the next screen pops back out of the corner. I'll drop a screen recording here. We haven't used anything other than the default transitions yet.