Anyone else able to solve the issue yet of the compose sources not being shown, and instead viewing the compiled .class file?

Hello! When

rememberScrollState

is used inside

Crossfade

, it receives different generates keys every time the screen is rotated. This prevents the state from being restored and also causes more and more keys accumulating in the

UiSavedStateRegistryAmbient

. Is it expected behaviour or a bug?

Have a question about theming. For things like typography, the values seem to be relatively static. However, if you look at material theme colors, those fields are specifically declared as mutable state and the constructor parameters are not properties, but simply values that are used for creating the mutable state instances. Why is this?

The mutableMapStateOf does not appear to maintain the order of the map when you iterate as mutableMapOf does. It randomly reorders my tabs. Any recommendations or is this a known bug?

Does Jetpack Compose have anything similar to the NavigationView in SwiftUI? Specifically: traversing deeper into a stack of screens with back button, swipe back to navigate, and of course the slide animation, etc. I know there is

ModalDrawerLayout

but that is more for a side menu..

I googled a bunch, but I couldn't find an answer to my question: How do you get the layed out height (or width) of a Compose component? I'd like to use the height of a LazyColunnFor to see if a ListItem is in the center of it (and scale it accordingly, based on how far away the ListItem is from that center).

Is there a relatively straight-forward way of removing the bottom indicator line in (filled) `TextField`s? I found

Modifier.drawIndicatorLine()

in TextField.kt but it's private. I could go ahead and make a “completely” custom text field using

BaseTextField

, I guess, it's just that

TextField

already had placeholders, leading/trailing icons and shapes and stuff built-in.

Hello, I am trying to align a card to center horizontal. But the new align is new working. Can somebody please help me figure out what am I missing/doing wrong.

@Composable

fun getSampleDataUI(list : List<SampleData>){

MaterialTheme {

LazyColumnFor(modifier = Modifier.fillMaxWidth(),

items = list) {item ->

ColumnScope.getSampleDataRow(data = item)

}

}

}

@Composable

fun ColumnScope.getSampleDataRow(data: SampleData){

return Card(modifier = Modifier.padding(15.dp).zIndex(5.0f)

.align(Alignment.CenterHorizontally)) {

Column(modifier = Modifier.padding(10.dp))

{

CoilImage(data.url, modifier = Modifier.size(50.dp).clip(CircleShape))

Text(text = data.value)

Text(text = data.value)

}

}

}

Another question 🙂 How can I mimic the Android views’

clipChildren=false

and

clipToPadding=false

?

Hi guys, one question, if have an existing app and I'm thinking to migrate some screens to compose, is there any problem related to the use of compose with

synthetics

?, should I use

dataBinding

or

viewBinding

instead of

synthetics

?

Why does compose have both Column and LazyColumnFor? It seems like everyone could just potentially benefit from using LazyColumnFor and getting rid of Column (or putting LazyColumn functionality into Column, and removing Column) could work? I only bring that up because I think I remember reading that @elihart said something along the lines of ~"Airbnb uses Epoxy even for lists that are completely heterogenous because RecyclerView will still only draw what needs to be on the screen which is a net benefit". I think Eli said that when someone asked like if using Epoxy was okay for using on all screens of an app, even the ones that don't even need a RecyclerView. Even taking Elis comments out (in case I'm imagining things) wouldn't just having a single abstraction for laying things out in a list be good for simplicity, and the list just knows how to "recycle" things if needed? Basically, theoretically wouldn't every list benefit from being in a RecyclerView/LazyColumnFor?

Are the performances of Compose in a ViewGroup (passed to

setContentView

in an Activity) the same as Compose at the root of an Activity, or is there layout render node related optimizations or whatever that cannot take place when Compose is used in a

ViewGroup

?

How would I go about constraining the top of one composable to the (vertical) center of another composable? I don't initially know the size of any of them. Is there a way to get the size of a composable post-measure? Thanks. 😒imple_smile:

I was updating to alpha04, but I saw gravity was deprecated and align was the automatic replacement. So i used Android Studio to replace it, but align wasn’t imported, and could not be. Except doing this by hand I noticed. Also the autocomplete for this is gone. Is this a known issue?

Any example about LazyColumnFor + LiveData + Pagination (Page3, LoadMore) etc ?

Is there a tool to convert an xml layout into an @Composable function? It could be useful for migration purposes

I'm experimenting with Compose interoperability. I have an xml layout that defines a debug drawer and then my compose view for the rest of the application. The debug drawer is a fragment with its own View using the regular Android View. The displaying Compose screen is a simple login form.

java.lang.IllegalStateException: KeyEvent can't be processed because this key input node is not active.

When I hit tab on the emulator to switch fields, I get this exception; is this attempting to forward the keyevent to the hidden drawer fragment? I'm unsure why adding the AndroidView would cause this

Hello, Regarding the issue downloading sources in latests AS versions: https://issuetracker.google.com/issues/169575797  The last comment says that the fix is coming in the first beta of 4.2. I was wondering if that’s coming any time soon, or if we’ll have to deal with that issue for a few more canary versions?

This is quite possibly the dumbest question ever, but how do I actually browse files on googlesource.com? Looking for the dev branch (I think

androidx-master-dev

?) so I can browse

compose/navigation/navigation/samples/src/main/java/androidx/compose

. It’s so different than github/gitlab and I have no idea why tapping the branch doesn’t take me to a directory of files

I am trying to a selector that picks a card and scrolls a card at a time. Is there a way to get a ScrollableRow or HorizontalList to snap on each item. Recommendations appreciated!! This is close, but no snap:

@Composable
private fun PagerLikeDemo() {
    val pages = listOf(Color.LightGray, Color.White, Color.DarkGray)
    LazyRowFor(pages) {
        Spacer(Modifier.fillParentMaxSize().background(it))
    }

}

What’s the best way to create a

Button

with a

LinearGradient

for the background? I see that the Button composable is not that hard to recreate, but internally using a

Surface

which takes a

Color

. Does this mean I have to recreate both

Surface

and it’s private composable

SurfaceLayout

to achieve a gradient background?

How do I enable P3 color for Jetpack Compose? I have

<activity android:colorMode="wideColorGamut" …>

in

AndroidManifest.xml

and using the colorSpace but it definitely does not look like the right color:

Color(red = r, green = g, blue = b, alpha = 1f, colorSpace = ColorSpaces.DisplayP3)

Apparently you can use Kotlin 1.4.20-M1, but just have to

kotlinCompilerVersion

set to 1.4.10 in

composeOptions

in

build.gradle

Is compose navigation ready?

Hi, anybody encountered this problem when upgrading to alpha04

Cannot import 'weight', functions and properties can be imported only from packages or objects

on Jetpack-Compose-Playground-master project?

Hello, I'm new to Jetpack Compose. I'm confused about how do Touch Events be handled by Compose. For example, if I want to write a custom view and handle touch events by myself. I could override onTouchEvent to do complex gestures before, but how could I do by Compose?

I know this has been discussed since

alpha04

came out, but I searched every answer here along with

compose-samples

. How do we horizontally center all children in a

Column

? This doesn’t compile:

Column(Modifier.align(Alignment.Horizontal)) { ... }

And this compiles but doesn’t do the job:

Column(Modifier.align(Alignment.CenterHorizontally)) { ... }

I’ve resorted to putting

Modifier.align(Alignment.CenterHorizontally)

on all the children within the Column, but I’m betting that’s not the intended solution.

Do we still use xml files for values? I've tried pruning the ones generated down but I still have colors, strings and 2xthemes files

Hi , How can I give layout margin around the view ? margin means the space outside the view, however padding means the space inside the view , why does it so complex to make here in the Compose ? I am not seeing any example of it ?