is it me or latest compose version broke animations api ?

Hey @Doris Liu are there any samples of how to use low-level animation APIs like Animation,

animate

and

AnimationState

?

How can I align composable function????

Modifier.align() has red line...

Hello , does SaveStateHandle do the same job? So we can use the ViewModel in the last saved state in another screen ??

In a nested lists

LazyColumn

of

LazyRow

items, it seems that the items of each

LazyRow

does not keep the values of any

remember

function across composition if the list is scrolled vertically. Is this a known issue?

How to use AnimatedContent to animate text changes, but also animate the initial value?

good afternoon composing team... is it possible to share a compose navigation graph between multiple Activities? my application has two acitvities that i wish to use the same nav graph. I have a main Home screen which is used for the majority of user triggered interactions however my app is also accessed via local notifications where i deeplink into another Activity which all works fine, however when the user clicks BACK or UP they are returned to the device Home Page where i wish for them to stay in my application

Do we know if they’re planning on building something like ImageComposeScene for Android? I need to render a Composable directly to a Bitmap. I’m aware of the workaround of creating a ComposeView and using the old View way of drawing to a bitmap, but is there a pure compose way to do this?

Hello, I would like to have a

LazyRow

, but with two specific requirements: 1. start centered on the 2nd element (I can scroll to it, but i would need some callback regarding the visible/centered element to be able to keep state after scroll) 2. the centered element should be slightly bigger than the rest (to be highlighted). But I have absolutely no idea how to do this. Do any of you have any idea or can you give me any tip on how to advance? Image added below to show the desired view

Some compose updates dropped today: Version 1.3.2 Stable released today. As far as I can see, nothing really tangible released. Should be an uneventful version bump. Version 1.4.0-alpha03 released today. LOTS of really cool changes! • Some animation updates, mostly related to testing it looks like? • Introduce

HorizontalPager

and

VerticalPager

, a way of showing composables in a Pager manner. Introduced

PagerState

to control the Pagers as well as query information about the Pager's current state. Introduced

PageSize

, a way of controlling the size of a Pager's page, this can be used to create a carousel like Pagers. Introduced

PagerSnapDistance

, a way to control how snapping will work in Pager's fling behavior. (I01120) • Introduced an overload in

SnapFlingBehavior.performFling

to help to understand where the fling will settle. (I569f6) • ^^ So it looks like accompanist pager is basically not needed anymore? cc: Chris banes? • Removed

OverscrollEffect#isEnabled

. • Added

ScrollableState#canScrollForward

and

ScrollableState#canScrollBackward

to query whether a

ScrollableState

has room to scroll in either direction • Added an Modifier API to query ancestors scroll info. (I2ba9d, b/203141462) • Used in

Clickable

to correctly delay press interactions, when gestures could become scroll events. • Fixed

Clickables

not correctly delaying ripples, when used inside an

Scrollable ViewGroup

. • Updated Drawers and Sheets to correctly delay presses in case gestures can become scroll events. • Update

snapStepSize

naming to be consistent with other methods in

SnapLayoutInfoProvider

. (Ife67c) • Added

EmojiCompat

to

Compose

(Ibf6f9, b/139326806) • Renamed

consumedWindowInsets()

to

consumeWindowInsets()

and

withConsumedWindowInsets()

to

onConsumedWindowInsetsChanged()

and made the Modifiers public. (Ie44e1) • Added

EmojiCompat

to

Compose

WOOO • Adding

@JvmDefaultWithCompatibility

annotation (I8f206) • Incorporated changes in the

Swipeable

APIs in

ModalDrawer

. `DrawerState`'s

animateTo

has been replaced by the

open

and

close

methods and the offset is now nullable. Use

requireOffset

to require the offset. (I3de9e) • Updated Drawers and Sheets to correctly delay presses in case gestures can become scroll events. • Fixed an issue where

PullRefreshIndicator

could get stuck after

onRefresh

is called, if the refreshing state was not changed to true. (Ie2416, b/248274004) • Add new default content padding for text button with icon to use. (I8f662) • Added disabled colors for navigation bar and rail. (Ia7892, b/258867034) • Snapshot apply notifications are now sent after the

Recomposer

finishes applying changes. (Iad6c0, b/222093277) • Added new wallpaper parameter to

@Preview

for dynamic colour support (I9f512) • Introduced changes in

captureToImage

to allow for capturing multi window screenshots. This is useful for screenshot tests that use compose PopUps. (I169c5)

Hi, I have a question for Scrollable View vertically.

Hi! Is there any Compose libraries for working with 3d graphics?

Hi. Is there a way in Compose to pass a container to another method and inflate stuff under that like for ViewGroup in xml

viewGroup.addView()

ViewGroup is passed to the method and i am using it as a container now to add more elements. Can i do similar thing in Compose? What i want to achieve is inflate my compose content under Toolbar (which is already created and the dynamic content needs to be added under that in later stage based on conditions and states)

Will there ever be a compose BOM for the alpha releases?

I’m trying to display dates in either 24 or 12 hour format based on user’s locale and preferences, but I’m noticing that changing date format in settings doesn’t cause a recomposition like I would expect… I tried reading

LocalConfiguration.current

like

resources()

does (https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:compose/ui/ui/src/androidMain/kotlin/androidx/compose/ui/res/Resources.android.kt;l=31-34?q=Resources.android) and I have

configChanges

added to manifest.

@Composable
fun LocalDateTime.localized(): String {
    LocalConfiguration.current // was hoping this would recompose when it changes, like resources() call
    LocalContext.current // same here
    val pattern = if (DateFormat.is24HourFormat(LocalContext.current)) {
        "H:mm"
    } else {
        "h:mm a"
    }
    // format the date:

anyone have any ideas?

Hi, how can I position a composable view at a percentage height of a composable container view? For example, centering a Text at the 20% of the height of its container.

Hey folk, is there any particular reason Jetpack Compose animations is not affected by these configurations from the Developers Options?

Hello! I am trying to write a compose test that toggles the selectable state of a selection chip. The selection state is handled outside the chip and would like to toggle it on the test rule. Currently

performClick

is not toggling the state. Do you have suggestions? Thank you! found the issue: I was not passing

selected

to the chip. 🤦

In the thread code, why I get a warning about returning a State without using remember?

Creating a state object during composition without using remember

Ran into this issue for the first time

Row {
  Box {
    AnimatedVisibility()
  }
}

this gives you an error

'fun RowScope.AnimatedVisibility(visible: Boolean, modifier: Modifier = ..., enter: EnterTransition = ..., exit: ExitTransition = ..., label: String = ..., content: AnimatedVisibilityScope.() -> Unit): Unit' can't be called in this context by implicit receiver. Use the explicit one if necessary

I understand that there are three

AnimatedVisibility

functions

@Composable fun AnimatedVisibility
@Composable fun RowScope.AnimatedVisibility
@Composable fun ColumnScope.AnimatedVisibility

But how do I invoke the first one without any scope?

I currently have the following composable:

@Composable
fun ColorPicker(
  modifier: Modifier = Modifier
) {
  BoxWithConstraints(
    modifier = modifier.aspectRatio(1F)
  ) {
    val diameter = constraints.maxWidth
    ...
  }
}

The problem is that it looks like if a user passes a

Modifier

to

ColorPicker

with size constraints, it would follow those. However,

BoxWithConstraints

uses the incoming constraints to size itself, not the constraints in its

Modifier

. In a case like this, should I be wrapping

BoxWithConstraints

in a

Box

that uses the

Modifier

parameter, or is it expected that the caller of

ColorPicker

should wrap it in whatever layout it needs, and set the size constraints appropriately?

How can i avoid my image looking like the first one, when it should look like the second one? (Not the color but the "resolution") They are both the same image, but one is displayed in browser and the other one in compose

I’m having a

LazyColumn

that should be always scrolled to the bottom (chat style list) I do that with

LaunchedEffect(listState.items) { scrollState....}

problem is that i have a list item that changes it’s size depending on an interaction this change is not picked up, bc. the items list itself is not altered. don’t want to expose the in-memory state if the item to the list so i could listen to it on list-level. is there any other way apart from providing a scrollToBottom callback down to the item - that it can call when it’s size changes?

Hi everybody - I came across a really strange recomposition issue that I'd like to better understand. We have a minimal state class containing a simple integer and boolean

data class ScreenState(val intValue: Int = 0, val boolValue: Boolean = false)

We have a screen composable that uses a composable based on the state. For the example we increment the integer value within the state once per second. Note that the boolean isn't modified.

@Composable
fun TestScreen() {
    // Screen state managed by the composable
    val screenState = remember { mutableStateOf(ScreenState()) }
    /**
    Update the integer value of the state once per second
    Note that the boolean value is never changed and is always false
     **/
    LaunchedEffect(key1 = null) {
        while (true) {
            delay(1000)
            screenState.value = screenState.value.copy(
                intValue = screenState.value.intValue + 1,
            )
        }
    }
    Box(
        modifier = Modifier
            .fillMaxSize()
            .background(Color(0xFF272727)),
        contentAlignment = Alignment.Center
    ) {
        // Simple composable that takes the state object as an input
        ContainerBox(screenState.value)
    }
}

The ContainterBox is an outlined column that takes the state in and uses the boolean to selectively include a composable using the integer value

@Composable
fun ContainerBox(value: ScreenState) {
    Column(
        modifier = Modifier
            .width(300.dp)
            .height(300.dp)
            .border(
                border = BorderStroke(1.dp, Color(0xFF23C42A)),
                shape = RoundedCornerShape(10.dp)
            )
            .clip(RoundedCornerShape(10.dp))
            .background(Color(0xFF75757A)),
        horizontalAlignment = Alignment.CenterHorizontally,
        verticalArrangement = Arrangement.Center
    ) {
        if (value.boolValue) {
            Text("Dynamic Text ${value.intValue}")
        } else {
            Text("Static Text")
        }
    }
}

The expectation is that since boolValue isn't being modified that ContainerBox wouldn't need to recompose. However, we see a recomposition every second. After quite a bit of debugging, we found the border modifier to be the culprit. If we take the border modifier out, the recomposition isn't performed until boolValue is changed. Does anybody know what about the border modifier is triggering the unneeded recompositions?

Hi all! It seems like material3-compose went to stable (latest version is 1.0.1) But there are still stuff annotated with

ExperimentalMaterial3Api

like Scaffold, which makes it a little bit confusing. Is it safe to use Experimental api in prod? Are there going to be breaking changes for that api?

Is there plugin to fold widget code of compose?