hey, question, i have a lazy column and inside i have an item that ,i need to check if it passed a certain y position, i know there is a remember scroll method but how can i check the y position?

Is there an issue with the

ComposableNaming

warning context window resolution? When I do it, the function name is capitalized properly, but it's usages are unchanged, causing compilation error. Shouldn't it do a proper function rename including references?

One more ... Has anyone else run into a problem with using a

WebView

(in an

AndroidView

) causing other Composables around the

AndroidView

to not get rendered? Defect filed here https://issuetracker.google.com/issues/174233728 , but I'm curious if anyone has run into this and found a workaround (also, if you want to star that issue while you're there, that'd be great 🙂 )

I think this may be related to this issue https://youtrack.jetbrains.com/issue/KT-38694 At least this strange workaround helped me: https://github.com/avdim/compose_mpp_workaround So I'm just letting know in case anyone else comes across this error

Hey everyone! I am trying to create a ComposeView (with just context) and then turn it into a bitmap… The reason is to generate a map pin marker for google maps with compose. Currently I do the following (the preview annotation generates a good pin image, the size I expect it to be)

val contentView = ComposeView(context = context).apply {
    setContent {
        ... composable ...
    }
    createComposition() // since no window is bound
}
val generator = IconGenerator(context).apply {
    setContentView(contentView)
}
val bitmap = generator.makeIcon()

If you debug the bitmap, you get a tiny (wrong size) drawing of the box’s shape, but not the entire rendered version of the shape. The generator is simple, and basically calls

composeView.measure()
composeView.layout()
composeView.draw(canvas)
canvas.toBitmap()

Does anyone have ideas of what might cause compose view to skip rendering? Or where to look to more deeply understand how compose is working behind the scenes?

Experiencing the same issues on alpha10. Is proper

AndroidView

support on lower level API like 24 planned before hitting beta?

Is Compose being developed on Wear OS, currently? I read it isn't (https://www.jetpackcompose.app/faq), but there is an issue regarding Compose on Wear OS in the tracker (https://issuetracker.google.com/issues/167438659).

FYI @Ben Lee contributed an example illustrating out to get jetpack compose working with bazel https://github.com/bazelbuild/rules_kotlin/pull/450

Created a demo of Slack's desktop app: https://twitter.com/vipul_asri/status/1350890351574175745?s=20

Hi, I have a question regarding ScrollableTabRow and edge padding is there a possibility to set padding only for the items inside, and not the left and right edge? simplified code: https://gist.github.com/piotrsedlak/4cd4994c91b4de2c59d7f6a1f5f1da12 What i need is: https://imgur.com/a/TbIbOVP but i get something like this, https://imgur.com/a/FspxhVU maybe i’m setting something wrong, or there is some internal padding that i cannot change? i managed to get something like i want using lazy row: https://gist.github.com/piotrsedlak/4fdb1b124e067e5ec8d50b933477bea7 https://imgur.com/a/DzM6IKy but that would mean implementing logic for the indicator, and if possible i’d like to avoid that

how to use different text colors with MaterialTheme? I saw an emphasis ambient (now called

contentAlpha

) but I want to describe 2 colors for diff emphasis not alpha.. how to achieve it?

Can anyone from Google confirm if accessibility support will be improved and documented for custom views in future versions of Compose?

Hi, how can I animate automatically for the children in ConstraintLayout when add or remove the

linkTo().

For example, a card will be animated to the center of the screen by pressing a button.

The slider

steps

parameter is not defined in the way I would expect. If I want a discrete slider to range from 0 to 12 in increments of 1, I would expect to specify steps = 12; however, I must specify steps = 11. Similarly, increments of 2 requires steps = 5 (not 6); increments of 3 requires steps = 3 (not 4); increments of 4 requires steps = 2 (not 3). The formula appears to be steps = (end - start)/increment - 1 when I would expect steps = (end - start)/increment. What is the rationale for the way it is defined?

@Composable
fun DiscreteSliderTest() {
    Column {
        val sliderValue = remember { mutableStateOf(5f) }
        Slider(
                value = sliderValue.value,
                onValueChange = { sliderValue.value = it },
                modifier = Modifier.width(400.dp) .fillMaxWidth(),
                valueRange = 0f..12f,
                steps = 3,
                )
        Text(
                text = sliderValue.value.toString(),
        )
    }
}

By the way, in the code example, the slider starts out with value 5, even though it is between quantized values 3 and 6 (if you move the slider you will never get it back to 5). That does not seem to be the desired behavior.

Sometimes syntax highlighting freezes and the IDE stops underlining errors. I had to do delete and reinstall, which brought no improvement.

Hello folks. I'm creating an app with Jetpack Compose and I want to use CameraX on my app. I need preview and videocapture. And beside them, I need beauty mode option also. For doing that, I should use vendor extensions. According to Android Studio's documentation, I should use vendor extensions. But there is no example for it or maybe I can't find. I wrote something like this but it does not work:

fun bindPreview(
    lifecycleOwner: LifecycleOwner,
    previewView: PreviewView,
    cameraProvider: ProcessCameraProvider,
    currentCam: Int,
) {
    val metrics = DisplayMetrics().also { previewView.display.getRealMetrics(it) }
    val screenAspectRatio = aspectRatio(metrics.widthPixels, metrics.heightPixels)
    val rotation = previewView.display.rotation

    val builder = Preview.Builder()
        .setTargetAspectRatio(screenAspectRatio)
        .setTargetRotation(rotation)

    val preview: Preview = builder
        .build().also {
            it.setSurfaceProvider(previewView.surfaceProvider)
        }

    val lensFacing = CameraSelector.LENS_FACING_FRONT
    val cameraSelector: CameraSelector = CameraSelector.Builder().requireLensFacing(lensFacing).build()

    val beautyPreviewExtender = BeautyPreviewExtender.create(builder)
    if(beautyPreviewExtender.isExtensionAvailable(cameraSelector)) {
        beautyPreviewExtender.enableExtension(cameraSelector)
    }
    
    try {
        cameraProvider.unbindAll()
        val camera = cameraProvider.bindToLifecycle(lifecycleOwner, cameraSelector, preview)
    } catch (exception: Exception) {
        Log.e(TAG, "Use case binding failed.", exception)
    }
}

bindPreview is called by "AndroidView" in a Composable method. Camera works perfect, but beauty mode is not working. Does anybody know about it ?

Folks, please don't @-mention us specifically for general reports and questions. My phone doesn't need to buzz for wrong website titles. 🙂

If I am not for myself, who will be for me? I've tinkered my way into a simple example: https://github.com/natanfudge/ComposeCompilerExample

This issue still occurs to me. I’m using compose

alpha09

and the insets are getting applied on the second time. Are there any more details you want me to share? I’ve tried to use

ViewWindowInsetObserver

but nothing changed. Any help would be much appreciated !

I've been trying this with a button unsuccessfully. Any ideas?

@Composable
fun LongPressButton() {

    val onLongPress = { _: Offset -> println("YAY!") }

    Button(
        modifier = Modifier.longPressGestureFilter ( onLongPress ),
        onClick = { /* Do something! */ }, colors = ButtonDefaults.buttonColors(
            backgroundColor = Color.Red
        )
    ) {
        Text("Button")
    }
}

👋 I’d like to draw a very small input field to hold just numbers (that should ideally be backed by a

Long

). It should look as simple as possible (no frills). Currently I’m trying with `BasicTextField`: is there anything else I may give a shot at?

Happy Friday y’all! Does anyone know the correct way to move the bottom sheet scaffold up to adjust for the keyboard in Compose? I’ve set layout param to adjust for soft input to achieve it, but there is an annoying jump between transitions.

Just released my first ever OSS library. Curious to gauge how useful people think the concept is: https://github.com/Chozzle/compose-macos-theme

I searched a lot but didn’t find any example showing how to have particular

TextField

pre-focused when a Composable is rendered, is this not recommended as per the best practices?

[This link](https://developer.android.com/jetpack/compose/interop) refers to [launchInComposition](https://developer.android.com/kotlin/androidx/compose/runtime/package-summary#launchincomposition), but it gives a 404.

Is it possible to handle volume key presses with

Modifier.onKeyEvent

(it doesn't seem to work in my code)? Or is the

Activity.dispatchKeyEvent

method a way to go?

I made a banner component but don't know how to achieve the move top-down animation. Can someone give me a hint? https://material.io/components/banners#behavior

hi, anyone knows how to achieve a snapToCenter behaviour with flingConfig and scrollableController? I’ve been watching the doogfooding sessions by Leland Richardson but wasn’t able to accomplish that “center item” behaviour when you drag the item and finish the drag with item uncentered. Anyone has any resource or know how to achieve this? thanks in advance

Sorry, there would have been, except we caught a last minute critical regression that ended up only getting caught when we did pre-release integration testing. We figured it would be better to avoid releasing something that would break everyone. We're working on finding a solution now, not yet 100% sure if this week's build release will be delayed or skipped.

We're trying as hard as we can! Just want to make sure that whatever we ship gets shipped with love! Will update you as soon as we know more!