Will we get something like

rootAmbient(MyAmbient

) or maybe all instances of the ambient above the tree?

Hey folks, got this issue where I compose some UI based on a model which shows either

TextInput

or

Text

when I double click on the text it turns the

Text

into a

TextInput

in the compose tree

@Composable
private fun Text(
    element: TextElement,
    inEdit: Boolean = false
) {
    val textStyle = TextStyle(
        background = Color.Transparent,
        fontWeight = element.fontWeight,
        fontSize = TextUnit.Em(element.fontSize),
        color = element.color
    )

    val spacing =
        Spacing(element.spacingLeft.dp, element.spacingTop.dp, element.spacingRight.dp, element.spacingBottom.dp)

    if (inEdit) {
        TextField(modifier = spacing, value = element.text, textStyle = textStyle, onValueChange = {
            element.text = it
        })
    } else {
        Text(modifier = spacing, text = element.text, style = textStyle)
    }
}

It seems that even though

Text

is being displayed Compose is still receiving text input via the missing

TextInput

(see video) possibly.. I would expect that if a recompose occurs then it would not exist in this part of the compose graph anymore 🤔 any ideas?

Hello! I’m trying to add a

TextField

in my screen but the component have a weird behavior. When I type any text in the text field, there isn’t any visual in the component on the screen. Someone has already encountered this issue? You can find my code here:

@Composable
fun Password(data: LoginForm) {
    MyTextField(
        hint = "Password",
        keyboardType = KeyboardType.Password,
        imeAction = ImeAction.Done,
        onValueChange = { data.email = it }
    )
}

@Composable
fun MyTextField(
    hint: String,
    onValueChange: (text: String) -> Unit,
    keyboardType: KeyboardType = KeyboardType.Text,
    imeAction: ImeAction = ImeAction.Unspecified
) {
    val typography = +MaterialTheme.typography()
    val model = +state { "" }
    Padding(left = 8.dp, right = 8.dp, top = 8.dp) {
        Column {
            Text(
                text = hint,
                style = typography.subtitle1
            )
            HeightSpacer(height = 8.dp)
            TextField(
                value = model.value,
                onValueChange = onValueChange,
                keyboardType = keyboardType,
                imeAction = imeAction,
                textStyle = typography.body1,
                modifier = ExpandedWidth
            )
        }
    }
}

Ping? https://kotlinlang.slack.com/archives/CJLTWPH7S/p1578991868120600

For me, the worst part about Compose is having to find all the dumb little tweaks to make the UI not look stupid, I got a

TextField

working (yay), but it looks awful and I wasted way too much time trying to figure out what I am supposed to ask for to get the border off the input…

I think this shows that Compose is not ready for its Hello World yet: https://gist.github.com/ErikHellman/d95ba1fa789e598a2ec6d40e69512b8d takes a lot of ugly little tweaks to make a form with 2 input fields..

Is there any known issue with having

@Model

annotated data classes in a different gradle module to where they are used in a compose tree? Just tried to move my model and when I run my app there are not recompositions when my model changes? 😞

I added a

<group>

tag into my vector drawable xml to rotate it 90 degrees and it shows up in preview but not in app with

DrawVector

shows up blank 🤔

Any update on release date for 'dev04' ?

@Leland Richardson [G] I previously saw your reply to one of the post here on slack where you shared a github gists link of a scrappy version of navigation arch component implementation that can be used with compose. Would you mind sharing that link again because i had a difficulty this morning finding that post you replied to with a link.

Giving a Surface composable a fixed height through modifiers does not work. Is that an expected behaviour of the Surface composable or a bug?

I am using

+onCommit

and it is working perfectly fine. But I am unable to understand when

onDispose

is called.

var user : User? = null
        // Active type use-case
        +onCommit(1) {
            user = UserAPI.getUserData()
            onDispose {
                UserAPI.letDiscompose() // It contains only println line
            }
        }

Is support for coroutines in compose coming soon or is it something not on the list of priorities yet?

I have two Column on FlexRow. One of the Column has

Arrangement.End

it doesn't expand into the right side of the view. Am I missing something?

Hi, I try to render a blue rectangle with fixed width and height, but it always fill the parent.

setContent {
            MaterialTheme {
                ColoredRect(color = Color.Blue, width = 100.dp, height = 50.dp)
            }
        }

But once I put a

Container

as the parent, it works as expected. May I know why?

setContent {
            MaterialTheme {
                Container {
                    ColoredRect(color = Color.Blue, width = 100.dp, height = 50.dp)
                }
            }
        }

I was reading there is a limitation using coroutines at the moment, what is the nature of the problem? I got this

Caused by: java.lang.IllegalStateException: Not in a frame
        at androidx.compose.frames.FramesKt.currentFrame(Frames.kt:180)

Is it related? happens when I use

IO

scope and not sure if its just me doing something wrong or I hit a known issue

Hi, I've been playing around trying to implement recycler "view" on Compose and this far for now: https://gist.github.com/ShikaSD/30ce3afc9376767f9ac090457733f627 Currently it only scrolls down and displays items correctly if you do it slowly 🙂 I have encountered an issue that layout in compose cannot add children synchronously. E.g. if recycler has some space at the bottom, it cannot be sure how many items it should lay out at once, as you cannot add and measure new items in the middle of layout pass. Currently my workaround is to keep a window of visible elements and increase/decrease it when items go out of the visible area. However, I add elements one by one (as I don't know how much space they will take) which is a bit slow (and require multiple passes to fill the screen for the first time). Do you have any suggestions on how to approach this better?

Hey composers, anybody got this stack yet? Not sure if prob between chair and keyboard or something known :)

I am trying to use Room with compose and kotlin. I know there is compability issue with

kapt

and

compose

and so that it throws

backend IR

error. But now in build gradle file i removed below line and it worked.

buildFeatures {
        compose true
}

Now even removing this line I am able to call compose function and load ui. So, what does this line means and its purpose.

We have to mark our classes with a @StableMarker annotated annotation in order to allow the compiler to perform the function skipping transformations. My question is why did you make this feature opt-in? We either have to annotate every class we use in compose with one of the annotations or we don't get the optimizations. Are there any plans to improve or change that behavior?

That is interesting. As it can often be the case that computation itself is cheaper than the args comparison. Doesn’t it make sense to opt-in for such behavior rather than having it as default?

Is there a simpler way to apply transformations such as rotate, scale, alpha and translate on composable in compose?

how is the way to call a composable inside an onClick?

FloatingActionButton(
    text = "aa",
    elevation = 7.dp,
    textStyle = (+typography()).body1.copy(color = Color.White),
    onClick = { Snackbar(text = "dsaf") }
)

java.lang.IllegalStateException: Composition requires an active composition context

When the ripple animation is bounded, it works fine on a rectangular shape but does not respect the bounds of a circular shape. In the short clip attached, you can see the animation respect the bounds on the list item not matter where you click or tap on the list item but with circular shape it is the opposite. Why is that so? Shouldn't the ripple behave the same with all shapes?

I am trying to retrive data from server(using retrofit). I am retrieving this data on

IO

thread. But as, I use this in below code, It will throw eroor

Not in a frame

fun<T> observer(data: LiveData<T>) = effectOf<T?> {
    var result = +state<T?> { data.value }
    val observer = +memo { Observer<T> { result.value = it }}

        +onCommit(data) {
            data.observeForever(observer)
            onDispose { data.removeObserver(observer) }
        }
//        commit()

    result.value

}

Hi! I have a pretty basic application. Basically it shuffles a list of ~150 strings. I’m concerned with performance. Recompose alone takes ~50ms each time. Full rendering is ~100-120ms / per shuffle. I realize this is a worst case for Compose (fully reshuffling 150 elements). Anything ideas how to improve performance? Code https://gist.github.com/tonsky/bca64aeb0c0e79151c39dd0e5a508d22

+imageResource(R.drawable.ic_arrow_core_lines_white)

do Compose support vectors?

Hi, I’m trying out Compose for the first time. I got a little stuck on the first tutorial where I’m supposed to draw an image with

DrawImage

. But I cannot seem to import the

DrawImage

function. Do anyone know what I might be doing wrong?