Made a Perlin Noise interpolator for Jetpack Compose Animation.

When using navigation component is it ok to use

navControler.graph.addAll(otherGraph)

/`navController.graph.addDestination()` after navigation has started? For example I want to dynamically decide, based on some user choice, that I want to add a whole bunch of new destinations. Will this work OK (+with composables in the graph)? Or is navigation component designed only so that whole graph must be constructed at once on the start?

I'm using a

mutableStateListOf<T>

but when I call clear() and then addAll() to it, it seems like compose tries to be "smart" and apply only the changes between the two lists. Is there a way to "opt out" of that behavior? So Im looking to go from this:

state.list.clear()
state.list.addAll(networkResult.newItems)

to something like this (completely made up api)

state.list.clear().commitTransactionAndWait()
state.list.addAll(networkResult.newItems).commitTransactionAndWait()

I have a

Column

inside a

Row

. The

Column

has a

Modifier.weight(1f)

inside if which fills the UI with a blank space. Once I add

Modifier.requiredHeight(IntrinsicSize.Min)

to the

Row

, the weight modifier wont work anymore (it will have width of 0. My

IntrinsicSize.Min

is applied to height only, why is it affecting the width of my items? Ill post some code in the thread

the trailing part of a ListItem with three lines doesn't seem to follow the spec (or look nice). The trailing part is put at the top of the ListItem. The spec says it should have 16 dp padding. Adding padding has no effect. Is there a workaround for this that doesn't involve writing my own ListItem?

https://developer.android.com/jetpack/compose/interop/compose-in-existing-arch#viewmodel says that ViewModels will still be tied to the lifecycle of the activity or fragment in which they were created. Is there any way to tie it to the "lifecycle of the composition" or should I use some DisposableEffects to reset view models' state?

Isn't there a way how to predefine multiple preview annotations and apply them on the preview composable? It would be much easier to to use something like

@MyCustomPreviews("component name")

which be equivalent of the following code

@Preview(name = "ProgressButtonPreview")
@Preview(name = "ProgressButtonPreview - night", uiMode = Configuration.UI_MODE_NIGHT_YES)
@Preview(name = "ProgressButtonPreview - scaled font", fontScale = 3f)
@Preview(name = "ProgressButtonPreview - en", locale = en)
...
@Preview(name = "ProgressButtonPreview - api 26", apiLevel = 31)

Hi, I'm trying to add password visibility toggle to a TextField but I cannot find Visibility icon. Do I have to install some extra libraries? I'm trying to use Icons.Filled.Visibility but Android Studio shows an error and is not able to import anything

Hi all, i have a text with maxLines 1, how to get overflow Ellipsis but for the first characters left instead of the the last characters right eg.

...lo world!

FYI: includeFontPadding & Compose https://issuetracker.google.com/issues/171394808

Not a really compose question, but I think,

ActivityResultContracts.TakePicture()

should return the file to match Compose declarative style. Currently, you have to create the file first, and keep a reference to it to use it after the camera intent finished successfully. Creating a

TakePicturePlus()

returning

Uri?

instead does not work, because the

TakePicture

result intent is almost empty.

Is there a way to set horizontal and vertical offset for

BadgedBox

, like it was possible for

BadgeDrawable

?

Hey everyone! Has anyone ever faced this issue while migrating to the latest compose and kotlin? My current compose version is 1.1.0-beta03 This error pops up when i try to update to 1.1.1 and 1.6.10 of Kotlin

The below code will print

B

null?.let {
    println("A")
} ?: println("B")

but the below code doesn’t render

B

null?.let {
    Text(text = "A")
} ?: Text(text = "B")

Why? 🤔

What's the non-lazy equivalent of

LazyVerticalGrid

?

I have a navigation back stack in my app that can be in one of two states: 1. Splash -> Home 2. Splash -> Landing -> Sign_In -> Home The following is the navigation code that navigates to the HomeScreen

override fun navigateToHome() {
    navController.navigate(RootScreen.Home.route) {
        val popUpRoute = navController.currentBackStackEntry?.destination?.route ?: ""
        popUpTo(popUpRoute) {
            inclusive = true
        }
    }
}

I would like to make sure that I can clear the back stack completely and then navigate to home. The way I understand navigation, calling popUpTo(currentScreenOnBackStack) should clear all the backstack before we navigate to Home and should account for both scenarios above. I’m sure I’m misunderstanding something obvious. Would appreciate if someone could point it out for me.

Compose animation has a slideInVertically transition. It animates from the top. Is there a way to animate it from the bottom?

Whats the best way to do State Management for compose , do anyone have some best approaches reads or sample I can take a look. I have tried state hoisting in viewmodel for `InputField`but it was bit messy since there was lot of state for error , label , placeholder and data . Any suggestions will be helpful

Can we restrict user to enter only alphanumeric chars in BasicTextField. E.g. we can do this in xml as follows ->

android:digits="abcdefghijklmnopqrstuvwxyz1234567890 "

Hi. I have 2 screens with videoview inside and i make transition between them using accompanist-navigation-animation lib. Transition between 2 compose “screens” is slow, i think it might be related to how i start videos, but i cant figure it out. Also when transition from first to second screen is made recomposition is run many times. Can somebody with more knowledge in compose please take a look how i handle video playback please. Thank you

How do I determine if this dropdown is overlapping the keyboard?

With Compose Navigation, let’s say you’re using BottomNavigation and you want a particular tab to remain selected as you navigate deeper.. I’ve seen something like this:

val selected = currentDestination
    ?.hierarchy
    ?.any { it.route == bottomNavItem.destination.route } == true

1. Is the idea that you have to leverage nested graphs in order for this to work? I’m sure this probably makes sense (because how else does Compose know that a particular destination belongs to the same hierarchy) So, assuming that is the case 2. If you have a screen that is accessible from two different Bottom Navigation roots.. You’d have to declare that route twice (once in each graph)? If that’s how it works, cool. Just want to make sure I’m thinking about this the right way

Is there a way to disable gestures on a Composable? I have a Composable that handles gestures I don't want (should just be a static read-only component). I tried this: https://stackoverflow.com/a/69146178, but my Composable is inside a scrolling Column, and it prevents scrolling the parent Column too, if you try to drag by my Composable.

I was wondering why

Modifier.swipeable

is part of

compose-material

, is there a specific reason? (I mean, it may be useful to non material design users - it also doesn't depend on any MD specific item, of course)

Does anyone know if kotlin 1.6 has finally stabilized the compiler api so that future versions of compose beyond 1.1.x won’t be so tightly coupled to the kotlin version?

Compose internally is saying there's something wrong with how I'm using the focus api. Code in 🧵

What is the best way to handle states that update more than 100 times per second?

Should InteractionSource.Hover enter/exit work when using a mouse or trackpad? (or something else work for mouseover visuals) With my Samsung tablet's trackpad I don't see any hover visuals in compose like I do with Views. I debugged it a little bit and found in AndroidComposeView.android.kt all the trackpad input events are ignored because they are hitting this condition:

if (event.isFromSource(InputDevice.SOURCE_TOUCHSCREEN) &&
    event.getToolType(0) == MotionEvent.TOOL_TYPE_FINGER
) {
    // Accessibility touch exploration
    return accessibilityDelegate.dispatchHoverEvent(event)
}

Keyboard navigation visuals work fine with the samsung keyboard, its just the trackpad thats not working

Hey everyone, I am working in a projects where I am planning to implement Navigation with Bottom bar.

implementation "androidx.navigation:navigation-compose:2.4.1"

compose version, I tried both 1.1.0 and 1.2.0-alpha04

I am trying to use this and where I create and add the bottomBar , I got Skipped * frames! The application may be doing too much work on its main thread* without adding any view. my code snaps -

@Composable
fun BottomNavigationBar(navController: NavHostController) {
    BottomNavigation(
        backgroundColor = AppColors.BottomNav,
    ) {
        val navBackStackEntry by navController.currentBackStackEntryAsState()
        val currentDestination = navBackStackEntry?.destination
        items.forEach { screen ->
            BottomNavigationItem(
                icon = {
                    Icon(
                        painterResource(screen.drawableResId),
                        tint = AppColors.secondary,
                        contentDescription = screen.route
                    )
                },
                label = { Text(stringResource(screen.resourceId)) },
                selected = currentDestination?.hierarchy?.any { it.route == screen.route } == true,
                onClick = {}
            )
        }
    }
}

@ExperimentalMaterialApi
@ExperimentalFoundationApi
@Composable
fun SportWorldUi() {
    val navController = rememberNavController()
    Scaffold(
        topBar = { TopBar(navController) },
        bottomBar = { BottomNavigationBar(navController) },
//        backgroundColor = Color.Transparent,
        modifier = Modifier.fillMaxSize()
    ) { innerPadding -> }

If I remove

bottomBar = { BottomNavigationBar(navController) },

, it works fine. Where is the issue here? Thanks