So I’m playing around with WebViews and I can’t seem to get the view to load changes. It appears frozen

Box(
        modifier = Modifier.fillMaxWidth() + Modifier.fillMaxHeight()
    ) {
        AndroidView(view = webView(ContextAmbient.current, "<https://google.com>"))
    }

fun webView(context: Context, url: String) = WebView(context).apply {
    loadUrl(url)
    settings.apply {
        javaScriptEnabled = true
        domStorageEnabled = true
    }

    webViewClient = client
}

Any ideas why it would be frozen?

Uhm, I think you guys will be forced to do something about widgets now as well 😄

Hi guys, I have one question, I just saw this in the androidx.ui.material package

/**
 * Contains the default values used by [Button]
 */
object Button {
    
    /**
     * The default inner padding used by [Button]
     */
    val DefaultInnerPadding = ...

    /**
     * The default disabled background color used by Contained [Button]s
     */
    @Composable
    val defaultDisabledBackgroundColor
        
    /**
     * The default disabled content color used by all types of [Button]s
     */
    @Composable
    val defaultDisabledContentColor
}

This is not only for the button but for many other views. I think a better naming for the object would be

ButtonDefalutValues

or

ButtonDefaluts

and remove the

default

suffix from all the properties.

Is there any concept in mind of how the composable should be decoupled or how big should/could be views/pages/screens with nested composable elements? Another question is, what is the best way to pass or get an instance of the ViewModel inside compose element?

Hi, I need an advice. I am developing a project with native mobile apps. Right now I am working with Kotlin for android (Coroutines, Flow, Clean Arch, MVI), and SwiftUI (Combine, Clean Arch, MVI). I am thinking to move to Jetpack Compose in the android app because it is very similar to the declerative UI in SwiftUI. You recommend to go for it? Or to wait when the Jetpack Compose will be ready for production?

Hello, is there any example with jetpack compose BottomAppBar? I can't manage my elements in it properly

I can use

rawDragGestureFilter

to move stuff around with one finger. Is there a modifier that allows to register multi finger touch? There is

scaleGestureFilter

for scale, but I can't find a way to do rotation with 2 fingers. What am I missing?

How to disable

Text

value from being selected on long press? I have a

Text

element inside

Button

and while I long click on button, its text is being selected. Could not find how can I disable it.

It seems like if there was not a user interaction (i.e. updating initial state from the server instead of a user action) the values don’t update. I use the same model for different controls and some work / some don’t.

Hi, I need an advice. I would like to call suspend function on

TextButton.onClick

. as

onClick

is not Composable. I can’t use

launchInComposition

so, I tried the below. but I’m not sure if this is proper approach or not. I searched on this channel but. it was difficult to find the discussion.

scope = remember { CoroutineScope(SupervisorJob() + Dispatchers.Main.immediate) }
onDispose { scope.cancel() }

TextButton(onClick={ scope.launch { doSuspendFunction() }})

what is the best approach on this case?

I'm trying to implement a modified WithConstraint. Linter says NodeLayout call doesn't take any argument, code compiles just fine, but it is not executed. I guess there is an internal NodeLayout Composable function which refers to the NodeLayout class, but I cannot find it. What is the proper way to use NodeLayout in my own code ?

Hi, I would like to anchor a floating action button to the edge of a bottom sheet. In xml I would use

app:layout_anchor

with

app:layout_anchorGravity

. Is this currently possible in Compose?

When using a scaffold with a conditional FAB, I find I have to cast to compile:

floatingActionButton = if (condition) { 
    @Composable {
        FloatingActionButton(onClick = {backStack.push(Routing.EditDrink(null))}) {
            Icon(Icons.Default.Add)
        }
    } as @Composable() () -> Unit
} else null

Or I get an "Expected type was Nothing?" error, but when casting the cast shows as a useless cast. Am I doing something stupid?

Is there something similar to Barriers in ConstraintLayout ?

Excited to try some of the new API’s that were just released!

I’ve just updated my demo for dev14, using the new ConstraintLayout DSL

I find that following the movement of

Toggleable

into a modifier, the bounds on the ripple applied are incorrect. I have the below code, but the ripple now extends to fill the full square bounds rather than the shape's bounds. How should this be rectified?

Surface(
        shape = RoundedCornerShape(8.dp),
        modifier = Modifier.toggleable(
            value = selected,
            onValueChange = { ... }
        )
) {
    ...
}

Do I need to do my own

RippleIndication

for this effect?

Is there any way to have a negative margin with constraint layout. I've tried using offset but this doesn't seem to move/resize other components which it is linked to

I am trying to use pixelcopy to capture the screen in a compose application, however, it asks for a view (which is kind of hidden in compose). What is the relationship between compose and views? How do I get the view currently being rendered by compose?

fun getScreenShotFromView(view: View, activity: Activity, callback: (Bitmap) -> Unit) {
    activity.window?.let { window ->
        val bitmap = Bitmap.createBitmap(view.width, view.height, Bitmap.Config.ARGB_8888)
        val locationOfViewInWindow = IntArray(2)
        view.getLocationInWindow(locationOfViewInWindow)
        try {
            if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
                PixelCopy.request(
                    window,
                    Rect(
                        locationOfViewInWindow[0],
                        locationOfViewInWindow[1],
                        locationOfViewInWindow[0] + view.width,
                        locationOfViewInWindow[1] + view.height
                    ), bitmap, { copyResult ->
                        if (copyResult == PixelCopy.SUCCESS) {
                            callback(bitmap) }
                        else {

                        }
                        // possible to handle other result codes ...
                    },
                    Handler()
                )
            }
        } catch (e: IllegalArgumentException) {
            // PixelCopy may throw IllegalArgumentException, make sure to handle it
            e.printStackTrace()
        }
    }
}

Hey guys if anyone speaks Spanish I’m going to give a small introduction into Compose this Friday at Android Dev Perú so if you want to check over if you’re starting go ahead and join

I’ve must have missed something about how the UI updates are handled. Before (when the magic of @Model existed) I could change the data model outside a @compose scope (data pushed via FCM) and it automatically updated the UI. Without that magic, I should according to the migration guide, I should use

by state

or

mutableStateOf

together with

remember

, both of them reassign the datamodel to a wrapped variable inside the @Compose scope and i’m not sure how to mutate the data class and force a refresh.

Hello everyone, I made a very simple app using compose and it crashes with the error :

java.lang.IllegalArgumentException: Key 640122159 was already registered. Please call unregister before registering again

The code can be found here https://github.com/bmonjoie/ComposeTipsCalculator I have seriously no idea what I'm doing wrong so if someone could give me any pointers, that would be really appreciated

I cannot find the constructor for

androidx.ui.core.LayoutNode(modifier = currentComposer.materialize(modifier), measureBlocks = measureBlocks) { childrend() }

Which is used in many base composable components. I would like to use especially the way LayzyItems using it to be able to add and remove Nodes during measurement runs. Why is it hidden from the Public API? Or maybe i just missed something?

https://twitter.com/intelligibabble/status/1273339533891788800 This tweet referes to using compose in any tree. Does this mean it can be applicable to kotlin/jvm for desktop? or even used in kotlin/js?

Hello, people from Flutter made an extensive document about state restoration and their plans (since it's not supported natively yet). When it comes to Jetpack Compose, I've not seen much about facilities to ease state saving (yet), so I'm wondering if that document could help shape the APIs that we can use to support state restoration easily. Here it is: https://flutter.dev/go/state-restoration-design

I need to make an animation for

Image

using an array of

DrawableResIds

. Let say to switch an image every second. Does anyone know how to achieve this using Compose animation API or transition? Or might there is some other way to do it?

Hi. My coworker @Jordan Carlyon and I are Android developers at the Wall Street Journal. We’re working on a joint initiative with our iOS and backend teams to create a Component Library that uses Jetpack Compose backed by JSON models. We successfully completed a concept thanks to the documentation and samples, but I haven’t found much information on the roadmap in terms of moving to alpha or beta. A level of parity with SwiftUI is important. Right now we’re debating whether or not it’s worth using Jetpack Compose in a small corner of our app or just building a standalone library and waiting to integrate until Jetpack Compose is more mature knowing that it could be a while. Any advice or general feedback would be helpful. Thanks!

Hi, I need an advice again. the code below hide ui if shown == false

if (shown) {
    Column {
        Text("Success")
    }
}

but, I would like to use the way below similar to data binding.(

android:visiblity="@{model.shown}"

) as it reduce indent depth, so, seems easy to read UI code. and feel better to separate ui and logic.

Column(Modifier.visible(shown)) {
    Text("Success")
}

I tried to customize Modifier. but, it looks difficult. is there any possible solution? or is it not recommended approach?

ListItem

icon is wrapped in a

Box

with

ContentGravity.TopStart

. I think that a Center Alignment would be more appropriate