[ Resolved ] Hi, I’m facing issue in animating transition in Compose.

var mProgress by remember { mutableStateOf(0F) }

val transition = updateTransition(targetState = mProgress, label = "")

Currently, On Button Click, I can easily change mProgress value and view will be animated But I’ve don’t want to animate on Button Clicked, rather the view should be animated as soon as it is displayed in screen. Tried a lot of things but no luck 😞 Any suggestion ?

Let's say I have a

Scaffold

and I show a snackbar by calling

scaffoldState.snackbarHostState.showSnackbar(...)

. The snackbar is shown above the fab. What can I do to make the snackbar move the fab up when it is shown and down when it disappears?

I have a

OutlinedTextField

and

var email by rememberSaveable { mutableStateOf("") }

inside single compose function. Upon rotating screen, email state value resets to

""

. Shouldn't

rememberSaveable

actually keep value of an email and not reset it?

I want to understand what is meant by "Unbundled from OS" In compose

When does a composable function go into composition and when does it leave composition? I can see I can call a Composable function for it to be displayed on the screen but how do you remove it?

When trying to use preview I get an error saying "PreviewActivity is not a Activity subclass or alias" . Anyone know how to resolve this?

Are there any plans for an autosized text in compose?

When using

AnimatedVisibility

how can I make the container scroll to show the item being expanded? (say I'm at the end of the scroll and there's an expandable item

What is the best way to force children composable to be placed in their parents ? I'm struggling with text rotation. I decided to rotate a row containing text instead of rotating each individual texts. I managed to keep proportion by switching width and height with a customer modifier, however I can't figure out how to force children element to stay at the position of their parent.

I'm experiencing memory leaks with compose 1.0 and navigation-compose 2.4.0-alpha05, which introduces crossfade. After a few navigations triggered by my bottom bar, i see multiple instances of my screen functions on the heap, one instance per navigation. They don't get garbage collected. No Leaks with navigation-compose alpha04. Anyone else experiencing this issue?

Is it possible to give an

OutlinedTextField

elevation with shadow? I tried to apply

Modifier.shadow(elevation = 8.dp, shape = RoundedCornerShape(8.dp))

directly to OutlinedTextField, but the result was horrible. Should I use

BasicTextField

instead? I see some

decorationBox

parameter in there, which might help.

I have a question about

HorizontalPager

. If each page have difference height then the

HorizontalPager

will match the size of the largest page is that correct?

For some reason the four images I put in a row do not fill the whole available width. Does anyone know why this is happening?

Row(Modifier.fillMaxSize().background(Color.Yellow)) {
    val pics = listOf(R.drawable.professor, R.drawable.woman,
    R.drawable.daughter, R.drawable.son)
    for (pic in pics)
        Image(painterResource(id = pic), null, Modifier.fillMaxWidth(0.25f).align(Alignment.Bottom))
}

Hi, does anyone know how to save/retain keyboard focus and cursor position for a

TextField

? I'm having a list screen with a search option and showing either list or error screen below the search box based on search results. It roughly looks like this for list state

Column{

SearchBox()

List()

}

and like this for error state

Column{

SearchBox()

Text("No results")

}

SearchBox

has

BasicTextField

and other decorations around it. Now when I start typing in the search box, the keyboard state and cursor position is retained for recompositions of the list screen update, but when the error state is shown, the keyboard is being closed and the

TextField

loses focus. The same happens when transitioning from error state to list screen.

Hi, I’m experiencing something weird with the compose compiler.

import androidx.compose.runtime.Composable
import androidx.compose.ui.graphics.BlendMode

@Composable
fun TestBlendMode(
    blendMode: BlendMode = BlendMode.Multiply
) {
    // Comment this line and compilation should work as expected
    val mode = blendMode
}

If i use a blendmode inside a composable, i get a crash. Anyone getting the same error with the 1.0.0 version?

: java.lang.AssertionError: Assertion failed
        at org.jetbrains.kotlin.ir.util.AdditionalIrUtilsKt.getPropertyGetter(AdditionalIrUtils.kt:236)
        at androidx.compose.compiler.plugins.kotlin.lower.AbstractComposeLowering.unboxValueIfInline(AbstractComposeLowering.kt:311)

I have this problem where typography is not reflected in Android studio preview? anyone facing same problem

Added a simple demo on how to implement a fullscreen tutorial overlay which highlights one of the buttons on the screen. In case someone was curious how to implement that in Compose. The code is here

In animation between screens (navigation) is available now ?!

Hi! 🙂 I have a usecase where I would like my LazyColumn to scroll to the top if I add a new item to the start of the list - but only if the list was scrolled to top before. Anyone knows how to do that? Think it's something like using a

LaunchedEffect

, but can't really wrap my head around it 🙂 I'm using keys so the list is in general keeping the same position when adding items 🙂

Hello everyone !) Can I use styles from xml with Text() composable function ?) Or I should rewrite all my style system ?

Hi! How can I create TextFild like that? I try:

TextField(
    value = titleState.value,
    onValueChange = { titleState.value = it },
    colors = TextFieldDefaults.textFieldColors(
        textColor = MaterialTheme.colors.primary,
        disabledTextColor = Color.Transparent,
        backgroundColor = Color.Transparent,
        focusedIndicatorColor = Color.Transparent,
        unfocusedIndicatorColor = Color.Transparent,
        disabledIndicatorColor = Color.Transparent
    )
)

The problem is when I want to put down text there is a text instead of hint and I have to delete text before typing the proper word

What this message means 'Modifier factory functions must use the receiver Modifier instance' When writing a modifier like fun Modifier.myModifier(i:Int):Modifier{ return Modifier.border(BorderStroke(1.dp,Color.Blue),RoundedCornerShape(6.dp))} It works as expected ...

Not strictly compose related... but I created a new app using the Compose template in Android studio. Does the status bar seem weirdly tall to you? I have NoActionBar, and only a statusBarColor set. Should I be doing something different in the theme for a strictly compose app?

<?xml version="1.0" encoding="utf-8"?>
<resources>
    <style name="Theme.MyApp" parent="android:Theme.Material.Light.NoActionBar">
        <item name="android:statusBarColor">@color/purple_700</item>
    </style>
</resources>

Is it expected that recomposition will not happen if the

data class

which represents my UI state contains a

var

and that var changes?

data class EventListState(val events: List<EventUiModel> = emptyList(),
                          var eventDestination: String = "", //Changes to this var do not cause recomposition
                          val pastEventsSelected: Boolean = false,
                          val isLoading: Boolean = true)

I'm trying to wrap my head around the navigation and I've got a bottom Nav bar that's working great so far and can switch between screens from the bottom. I need to implement stack views with back buttons inside each bottom nav bar tab. So when a user starts switching views inside a tab the current screen sticks if they click on another tab the state of the other tab is remembered. I'm reading over this (https://medium.com/google-developer-experts/navigating-in-jetpack-compose-78c78d365c6a) and it looks like kind of like what I need but unsure how it jives with a bottom nav bar. And this is my bottom nav bar that I pulled out of a demo app

@Composable
fun Navigation(user: FinUser, navController: NavHostController) {
    NavHost(navController, startDestination = NavigationItem.MapScreen.route) {
        composable(NavigationItem.Account.route) {
            Account(user = user)
        }
        composable(NavigationItem.History.route) {
            History(user = user)
        }
        composable(NavigationItem.MapScreen.route) {
            MapScreen(user = user)
        }
        composable(NavigationItem.Promo.route) {
            Promo(user = user)
        }
        composable(NavigationItem.Help.route) {
            Help(user = user)
        }
    }
}

@Composable
fun BottomNavigationBar(user: FinUser, navController: NavController) {
    val items = listOf(
        NavigationItem.Account,
        NavigationItem.History,
        NavigationItem.MapScreen,
        NavigationItem.Promo,
        <http://NavigationItem.Help|NavigationItem.Help>
    )
    BottomNavigation(
        backgroundColor = MaterialTheme.colors.primary,
        contentColor = Color.White
    ) {
        val navBackStackEntry by navController.currentBackStackEntryAsState()
        val currentRoute = navBackStackEntry?.destination?.route
        items.forEach { item ->
            BottomNavigationItem(
                icon = { Icon(item.icon, contentDescription = item.iconName) },
                label = { Text(text = item.title) },
                selectedContentColor = Color.White,
                unselectedContentColor = Color.White.copy(0.4f),
                alwaysShowLabel = true,
                selected = currentRoute == item.route,
                onClick = {
                    navController.navigate(item.route) {
                        // Pop up to the start destination of the graph to
                        // avoid building up a large stack of destinations
                        // on the back stack as users select items
                        navController.graph.startDestinationRoute?.let { route ->
                            popUpTo(route) {
                                saveState = true
                            }
                        }
                        // Avoid multiple copies of the same destination when
                        // reselecting the same item
                        launchSingleTop = true
                        // Restore state when reselecting a previously selected item
                        restoreState = true
                    }
                }
            )
        }
    }
}

This

composable(NavigationItem.Help.route) {
            Help(user = user)
        }

makes sense for doing top level routing but what about nested routing?

The new navigation_compose 2.4.0-alpha05 introduced crossfade. At the moment i used "Scaffold per Screen". Each screen in the application has its own Scaffold because some screens should show an docked FAB in the BottomBar. Now, with navigation 2.4.0-alpha05, my blue BottomBar flickers on every navigation, because of the crossfade. I think the solution is to put the scaffold out of the screens -> One global Scaffold Could someone give me an example on how to use the navigation library in compose with one Scaffold around the NavHost. Screen A should not show a fab, Screen B should show the docked FAB. My problem is the fab click handling

How to handle press down and up events?

We’re implementing a custom Switch component, and noticed that we have to do some math with the

SwipeableState.offset

when the layout direction is Rtl to draw the thumb on the right side. The gesture direction is correct though. Should

SwipeableState.offset

return inverted values in Rtl mode? If so, I can file a bug.