Does any1 know what is the color for this bubble ?

Compose v1.0.3 supports Kotlin 1.5.30🎉

Shouldn't

textAlign = TextAlign.Justify

mean the whitespace is stretched to fill the width? Or am I misunderstanding

TextAlign.Justify

?

Text(
  "heebie-jeebies ".repeat(4),
  Modifier.fillMaxWidth().background(Color.Yellow),
  textAlign = TextAlign.Justify
)

A transparent to white

Brush.verticalGradient

in a white

Box

renders gray with

drawWithCache

. A bug? Code in 🧵

Hi everyone. Why I cannot use a ScrollableColumn/LazyColumn inside another ScrollableColumn/LazyColumn?

Is there any way for fillMaxSize to work with rotation. It works fine when view is a lot smaller than than device width and height but as it gets larger it starts to deform. I tried to do it with BoxWithConstraints and flip between width and height but it is still deforming when rotated.

it it possible to disable the label animation for OutlinedTextField? I have label and placeholder. I don’t want the label to jump around

While I appreciate generating random numbers in a @Composable is a bad thing to do, I don't think the following should fail to @Preview? (See thread for exception)

@Preview @Composable
fun PreviewTest() { Random.nextBoolean(); Text("Hello World") }

I want to draw text on a canvas like the below picture. variable2 can be null but the text should always be in the center. How can I measure or draw this kind of multiline text perfectly in the center?

how can i change the LocalTextSelectionColors ? i used the same approach as the colors in jetsnack, but for some reason it keeps the original ones

Hi, what would be the best way to prevent unneeded AnimatedVisibility on new Configuration, for example when orientation changes?

Is there any recommended practice to expose some composable internal state, but keeping it updatable only internally? For instance, i have this inside the composable:

val hasError by remember(textFieldValue.value) {
    derivedStateOf {
        textFieldValue.value.text.isNotEmpty() && isInputValid(textFieldValue.value.text).not()
    }
}

I want the caller code to access this value, but i don’t want to change it outside

How can I add a

onLongClick

event handler to a button? There is no parameter in the constructor. I tried with

Modifier.combinedClickable

with a

onLongClick

event listener. But it isn't working.

Column(modifier = Modifier.padding(30.dp)) {
        Button(
            onClick = {
                Toast.makeText(
                    applicationContext,
                    "hi",
                    Toast.LENGTH_SHORT
                ).show()
            },
            modifier = Modifier.combinedClickable(
                onLongClick = {
                    Toast.makeText(
                        applicationContext,
                        "hello",
                        Toast.LENGTH_SHORT
                    ).show()
                },
                onClick = {}
            )
        ) {
            Text(text = "Click Me")
        }
    }
}

given an already created MutableState, how can i update it when some other MutableState changes?

Card shadows are cut off when using

Modifier.alpha

, due to the underlying call to `graphicsLayer`; is there a way to work around this?

In a 100% Compose app, is it possible to get rid of the com.google.android.material:material dependency, since it has transitive appcompat dependencies..? It seems to be required only for the theme inside themes.xml, which itself is only required for the theme referenced from the AndroidManifest?

Whenever i have the keyboard opened on some field, and i click on a button that changes fragment, this error happens

Working on RTL support for compose, and everywhere it is recommended to use

CompositionLocalProvider(LocalLayoutDirection provides LayoutDirection.Rtl){
}

I only want this to happen when the locale is RTL, is there any efficient way to find out what layout direction should be used?

🧪 When testing screen orientation change, am getting

java.lang.IllegalStateException: No compose views found in the app. Is your Activity resumed?

➡️ More details in the SO thread

I built a composable function with the intent of reusing it in places in my app that want to show a Grid similar to the legacy android GridLayout. But compiling it gets this error with a long callstack:

org.jetbrains.kotlin.backend.common.BackendException: Backend Internal error: Exception during IR lowering
File being compiled: <path>/GridDisplay.kt
The root cause java.lang.IllegalStateException was thrown at: org.jetbrains.kotlin.backend.common.lower.loops.RangeLoopTransformer.gatherLoopVariableInfo(ForLoopsLowering.kt:375)

Anyone else seen this? I started stripping stuff down and have a small function now that doesn't do much but builds fine, then a change to one line causes the build to fail with this error. I'll post the good code/failing code in a thread in case someone is interested. Weird. Searches show a similar error when trying to use kotlinx serialization and compose in the same module, but I don't have that scenario. My app does have three multi-platform modules using serialization, but the app module specific to android and using compose does not use serialization. Would this be a jetbrains defect or a Compose/google defect? Thanks in advance for any suggestions. FWIW this happens with kotlin 1.5.30 and compose 1.1.0-alpha04

Hi, i am using accompanist permissions

@Composable
fun MyComposable() {
    val cameraPermissionState = rememberPermissionState(Manifest.permission.READ_CONTACTS)
}

I am getting the following error `

java.lang.IllegalStateException: Permissions should be called in the context of an Activity

`

If I have a full edge to edge app (so my status bar is transparent), and I open up a bottom sheet full screen... it goes all the way up behind the status bar. Where would I add my status bar insets so that the bottom sheet doesn't go all the way to the top?

Is anyone using dependency injection / oop for theming in compose? I see a lot of top level declaration in samples / material documentation

📢 ✏️ All Compose users, please consider voting for this issue in the google Issue tracker I know everyone wants their issue voted for - but really... this is a big one! If you have ever or will ever put a

TextField

inside a scrollable area then this affects you. Currently, Compose does not maintain visibility of focused elements inside a scrollable viewport, when it shrinks. This affects the very common case, where a user taps a Text Field and keyboard pops up. Often the field will become hidden behind the keyboard due to the viewport not scrolling (this is not an Activity

adjustResize

or Insets issue). Currently the only workaround is a hacky solution with a delay and

RelocationRequester

. This needs a proper solution!

Compose will eventually arrive for ios, right? If so, will it run on native or jvm?

Hello community. I am trying to find a way to make stateful composable that knows new and previous state upon the change. I would like to make an action that takes old value as parameter when the new value comes. Is taht possible using some sideEffect? I tried, but with no luck so far. More in 🧵 👇

What's the right way to dim the screen brightness in Compose? Do I need a reference to the activity?

Can I put this

(context as Activity).apply {}

block directly into the composable function or do I have to wrap it into one of the side effects methods? I just can't wrap my head around it.

@Composable
fun TimerScreen(
    viewModel: TimerViewModel = hiltViewModel(),
) {
    val uiState by viewModel.uiState.collectAsState(null)

    val context = LocalContext.current

    [...]

    val screenBrightness = if (uiState?.timerRunning == true) 0.15f else -1f // default

    (context as Activity).apply {
        val attributes = window.attributes
        attributes.screenBrightness = screenBrightness
        window.attributes = attributes
    }

    ScreenContent(
        uiState = uiState,
        actions = viewModel,
        scaffoldState = scaffoldState,
        bodyScrollState = bodyScrollState,
    )
}

Quick question. Why back (◀️ ) button first drops focus from `BasicTextField`❓ So in order to go back from a screen with input I need to click back button twice ❗

If I'm using multiple MutableStateFlow instance fields for individual settable options of a composable, then using collectAsState inside the composable. Is there any guidance as to whether to use 6 individual fields, vs a single combined field with a data class. Do 6 State instances (of primitives, like Int / String) perform worse than a single State instance with that data class.