Is there a guarantee that when working with `Layout` the ord kotlinlang #compose

Channels

100daysofkotlin

100daysofkotlin-2021

algolialibraries

android-architecture

android-databinding

androidgithubprojects

androidx-xprocessing

arrow-contributors

beepiz-libraries

cincinnati-user-group

codemash-precompiler

codingconventions

competitive-programming

competitivecoding

compose-android

compose-desktop

compose-ui-showcase

connect-audit-events

cscenter-course-2016

domain-driven-design

effective-kotlin

effectivekotlin

embedded-kotlin

event21-community-content

fb-internal-demo

fluid-libraries

framework-elide

getting-started

github-workflows-kt

graviton-browser

image-processing

intellij-plugins

intellij-tricks

introduce-yourself

java-to-kotlin-refactoring

jhipster-kotlin

jvm-ir-backend-feedback

k2-early-adopters

kotest-contributors

kotlin-by-example

kotlin-data-storage

kotlin-foundation

kotlin-in-action

kotlin-multiplatform-contest

kotlin-pakistan

kotlinforbeginners

kotlingforbeginners

kotlinprogrammers

kotlintest-devs

kotlinultimatechallenge

kotlinx-datetime

lambdaworld_cadiz

language-evolution

language-proposals

leedskotlinusergroup

library-development

machinelearningbawas

myndocs-oauth2-server

navigation-architecture-component

ohio-kotlin-users

pattern-matching

pocketgitclient

practical-functional-programming

prozis-android-backup

python-contributors

realworldkotlin

refactoring-to-kotlin

refreshversions

russian-kotlinasfirst

skia-wasm-interop-temp

sofl-user-group

spring-security

squarelibraries

stayhungrystayfoolish

strife-discord-lib

swagger-gradle-codegen

swiss-user-group

tricity-kotlin-user-group

Title

e

eygraber

05/23/2023, 6:14 AM

Is there a guarantee that when working with

Layout

the order of

Measurables

in the

MeasurePolicy

will be in the same order that the content composables are emitted?

s

Stylianos Gakis

05/23/2023, 7:51 AM

However, it might be easier on your eyes and your brain to do what TextField for example does by tagging each item with a layoutId and reference that later to measure it and whatnot. See here in line 530 and then in line 650 for example. https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:compose/[…]Main/kotlin/androidx/compose/material3/TextField.kt;l=530-650

e

eygraber

05/23/2023, 12:08 PM

Good to know, thanks (I was using parent data for that in some cases). I'm asking for a case where there will be a dynamic amount of children of the same type

e

ephemient

05/24/2023, 12:34 AM

you do have to be somewhat careful because

@Composable fun Foo() {
    Bar()
    Baz()
}

Layout(
    content = {
        Foo()
    },
    measurePolicy = { measurables, constraints ->

can result in your measurePolicy receiving

measurables.size != 1

the <https://developer.android.com/reference/kotlin/androidx/compose/ui/layout/package-summary#Layout(kotlin.Function0,androidx.compose.ui.Modifier,androidx.compose.ui.layout.MeasurePolicy)%7C@Composable fun Layout(contents: List<@Composable () -> Unit>, modifier: Modifier = Modifier, measurePolicy: MultiContentMeasurePolicy ): Unit> overload doesn't have that issue because each item of the list is put into its own group so there's a 1:1 correspondance

2 Views

#compose Join Slack