Why is the order important for the modifier (fillMaxSize() vs padding()) in Android Jetpack Compose?

paulFEBypaulFE

Hello,

Why is the order important for the modifier (fillMaxSize() vs padding()) in Android Jetpack Compose?

I get for the modifiers:

  • Modifier.fillMaxSize().padding(16.dp)
  • Modifier.padding(16.dp).fillMaxSize()

Not the same result.

The latter creates a smaller composable -> but since one acts on the outside (fillMaxSize) and the other on the inside (padding), it shouldn't matter in my opinion in which order I define it.

Just like with HTML.

(1 votes)
Loading...

Similar Posts

Subscribe
Notify of
1 Answer
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
Erzesel
Erzesel
6 months ago

In advance:

I am not a jetpack programmer and can only draw logical conclusions from the (fastly flying) documentation…

see Padding:

Jetpack Compose doesn’t have a modifier for margin. We should use the padding modifier for both padding and margin. (Depending on the position/order in a sequence of formattings.)

@Composable
fun TextWidthPadding() {
    Text(
        "Padding and margin!",
        Modifier.padding(32.dp) // Outer padding (margin)
            .background(color = Color.Green) //background color
            .padding(16.dp) // Inner padding
    )
}

in your case this would mean that a pudding() before Fillmaxsize() as Margin act. Padding() After Fillmaxsize() as Padding

***Declaration under reservation that it is not my area of expertise! 😇

1