Compose Version 1.2.0-beta03 released! 😛arty-parrot: Lotsa small cool stuff. (this is just my opinion from release notes + commit messages) • Added Experimental Easing Curves for Animations • Added new experimental

IntervalList

and

MutableIntervalList

. It allows to represent some list of values via multiple intervals. It will be useful when you want to define your own dsl similar to the one used by

LazyColumn

where list items can be defined via multiple item/items calls. (I2d05e, b/228580728) • Clarified the documentation for

WindowInsets.ime

to state that

ime

insets are reported as far back as API 23, but only animated on 30+. (Ia7fc0, b/230756508) • Pressing the forward delete key when the cursor is at the end of a text field will no longer crash. • Fix incorrect offset calculation for Modifier.animateItemPlacement() in lazy lists • Fix for stretch overscroll clipping the shadow (OHHHH YEAHHH. This made carousels look kinda bad. 💯 ) • Show selection handles in read-only text field • Fixed a bug where

BottomSheetScaffold

was drawing over the top app bar's shadow.

BottomSheetScaffold

now also takes the sheet's state into account when placing Snackbars: in the collapsed state, Snackbars are placed above the sheet and FAB; in the expanded state, Snackbars are anchored to the sheet's bottom. (thanks Jossi 😄 ) • Fix Material outline text field label measurement • Fix inner text field position of the OutlinedTextField when label is multiline • Clean up invalidated compositions during disposal • Fix derive state read during recomposition ("sometimes causing infitinite recompositions" ?) • Baseline profiles for compose should be derived using benchmarks. • The

Show Layout Bounds

setting will now be applied for composables immediately after toggling it from the quick settings tile, without having to leave and re-enter the activity. (OHHHH YEAH) • Some minor fixes for custom font stuff • Material3 Version 1.0.0-alpha13 released

How can I perform an action when the user closes the keyboard? All i can find is how to handle ImeAction clicks. I want to call focusManager.clearFocus() no matter how the user closes the keyboard.

Is there a way to use the system default font in Compose? Seems Samsung users loves to change their font.

How do I animate a new element entering the composition? Like if I have a

Column

with a variable number of items and I want a new item to slide in when it’s added.

AnimatedVisibility

doesn’t seem to be the right solution, because the content is not visible/invisible, it just doesn’t exist before it’s added.

Hey there! Does Jetpack Compose require gradle? We are looking at ways to be able to use Compose with a project that uses Soong for one of our shared libraries, but where the Soong version needs to build it from source without gradle.

is there any padding equivalent, optimised with graphics layer =?

I want to use an XML layout for a custom view inside my compose view. the problem is the constructor my custom view takes

Context

and

AttributeSet

from Compose I can pass only the

Context

is there a way to pass the

AttributeSet

?

I have an issue with

Text

that I think might be a bug in the framework. Basically, when I put a

height(x.dp)

modifier on a

Text

, but the text is too long, the last line appears outside the bounds of

Text

. More in thread.

Other than manually putting in dividers between each element, is there a good way to put a divider between elements of a column? I’m not convinced a vertical arrangment can insert some sort of composable, or force any drawing. It seems to only be able to position items that are already children.

What is the recommended way to handle these false positive warnings about

Add permission check

in composables?:

Call requires permission which may be rejected by user: code should explicitly check to see if permission is available (with checkPermission) or explicitly handle a potential SecurityException

With Android 12 this shit becomes really confusing. Anything that is not like:

if (ActivityCompat.checkSelfPermission(
            this,
            Manifest.permission.BLUETOOTH_CONNECT
        ) != PackageManager.PERMISSION_GRANTED
    ) {
        // TODO: Consider calling
        //    ActivityCompat#requestPermissions
        // here to request the missing permissions, and then overriding
        //   public void onRequestPermissionsResult(int requestCode, String[] permissions,
        //                                          int[] grantResults)
        // to handle the case where the user grants the permission. See the documentation
        // for ActivityCompat#requestPermissions for more details.
        return
    }
    val deviceName: String? = sharedPresenter.connectedDevice?.name // no warning

will be reported as if the permission has never been granted, which is technically wrong. But the example above is no real world use case and also verbose and leads to duplicated code. That's why accompanist has its

rememberPermissionState

API. But using this API does not prevent the warning.

When using

MaterialSharedAxis

transition for fragment with

ComposeView

getting crash when pressing back button, Full question in Thread

What exactly is Mario scrolling :blob-sweat-smile: ? https://android-review.googlesource.com/c/platform/frameworks/support/+/2063892

Someone knows why individual item shows

Divider

and

LazyRow

hides

Divider

?

This message was deleted.

Hey guys, is there a way to measure pressure events on touch, i know it could've been done with gesture detector previously in the view system but I can't seem to find anything in Compose?

Is this channel exclusive for android compose or is it for compose in general?

Is there a library function to collect a StateFlow to State without being @Composable? It is, I think, pretty trivial to do myself, but I can imagine it is a pretty common pattern in something like a ViewModel?

class AppViewModel(val someExternalStateFlow: StateFlow<Something>, val scope: CoroutineScope) {
   private var _state = mutableStateOf(someExternalStateFlow.current)
   val state: Something by _state

   init {
     someExternalStateFlow.onEach { _state.value = it }.launchIn(scope)
   }
}

Something like this:

fun <T> StateFlow<T>.collectAsState(scope: CoroutineScope): State<T> {
    val state = mutableStateOf(this.value)
    this.onEach { update -> 
        state.value = update
    }.launchIn(scope)
    return state
}

Is there any particular reason why compose does not support method reference in @Composable functions? Is it a design decision or just a current limitation?

I'm trying to understand how to read the Recomposition Counts in Layout Inspector. It looks like there might be a problem with my text. Could someone please have a look at my screenshot in thread?

does anyone know and can link sample that has items being swiped in both left and right, swipe left to dismiss (item disappears) and swipe right to complete, select etc. (item remains on the screen)?

val multiSelectionEnabled = rememberSaveable{mutableStateOf(selection.isNotEmpty())}.value

Will changing selection, trigger a recomposition? Can this be used instead of using delegates?

Hi there! Is there any way to block scroll to the left in HorizontalPager? I want to allow scroll to the right only

👋 Are the new experimental context receivers usable with Composable functions? I’ve tried playing around with some basic examples but keep running into

Backend Internal error: Exception during IR lowering

, wondering if I’m doing it wrong or if it’s just not supported yet

Hi, I'm learning Compose and trying to re-implement a rectangle with a border only on 3 sides. In the old school way, I created a drawable with a negative offset, but in the world of Compose I'm not sure what the equivalent would be. Any ideas what I should try?🧵

I would like to propose a "new" kind of Compose state management instead of Redux-like solutions.

I'm trying to figure out how to pass arguments to the start of my compose nav graph. I haven't worked with composable navigation before and I'm most likely doing things in an unrecommended way a bit, but here's a little more detail with what I'm trying to do. I've got a fragment with a ComposeView, and that composable content contains the composable nav graph...the simplified version is something like this:

fun SomeComposableContent(startRoute: String) = 
    NavHost(
        route = "outer",
        startDestination = "inner/{userId}"
    ) {
        navigation(startDestination = "inner/start/{userId}", route = "inner/{userId}" {
            composable(route = "inner/start/{userId}") { backEntry ->
                val userId = backEntry.arguments?.getString("userId")
                ScreenOne(userId)
            }
        }

        composable(route = "next") {
            ScreenTwo()
        }
    }

If I use the "next" destination as my start and then navigate to the inner graph with passing an arg, things work, but if I want to start at the inner start destination, and I'm not calling navController.navigate(), how can I pass the argument? I'm basically trying to load the graph and pass the argument..is that possible?

Hello, After installing the app built with Jetpack Compose. It seems that Text shows different weights on different devices ? How to resolve this to keep this constant ??

Can I reuse a node in Jetpack Compose? With the View system, I can remove a view from its parent, then add it to another container. How can I achieve this with Compose?

Did anyone ever encounter a

SnackBar

duration issue where it always shows 10seconds in emulator and works fine(4 seconds)on the real device (with

duration = SnackbarDuration.Short

)? really odd. • No developer settings to change animation