hi I'm using navigation compose & my requirement is to have startDestination as list or detail page. Got no issues with list but for detail I need to pass detail id, more in the thread

Compose doesn’t differentiate between touch mode vs not-touch mode focus, right? Does Compose’s focus model just assume keyboard navigation isn’t a thing? I don’t see anything in the implementation of Material

Button

that interacts with the focus system.

Hi, I'm running the

AnimatingCircleTests

from the

Rally

sample app, and after creating an emulator with 420 dpi I can't seem to troubleshoot the reason the tests are failing. According to the logs I tried creating there should be temporary files created at

/data/data/com.example.compose.rally/files

but that folder seems to never get created, so the question is • how should I compare the golden image to the actual screenshot generated during the test?

Wrote some thoughts on using Jetpack compose and how to think of UI’s in compose land 🙂. would appreciate feedback if any 🙂 https://learning-to-code.hashnode.dev/declarative-ui-in-android

Hi there! I am learning about Jetpack Compose. I read on Android pages, I see many advantages about it, but I haven’t implemented it in my project. I want to hear some points of you, guys. What do you thing about Jetpack Compose ? Should or shouldn’t use it in the further ? or Have any disadvantages about it ? … Thanks for your helps, guys. Happy coding.

Does any having the issue

java.lang.IllegalStateException: LayoutCoordinates androidx.compose.ui.node.InnerPlaceable

after enabling accessibilty service when using compose beta05? Full stacktrace in thread

👋 Just here to throw some random hope as the Google IO starts today 1️⃣ . 0️⃣ 👀

Hello here. I have implemented paging with compose but instead of using LazyColumn, I wish to use a LazyVerticalGrid with two cells each.How do I use lazyPagingItems in LazyVerticalGrid?

val lazyPagingNotes = viewModel.notes.collectAsLazyPagingItems()

Advice please how to correctly establish typography in compose project for day-night theme if i want to use

color

parameter in each

TextStyle

? I see next options 1. use resources and separate colors by folders. Good for theming, because all happens authomatically, but i don’t understand yet how to create Color from resource without @Composable

colorResource

2. use colors preset from kotlin code. In this case all variants that i can imagine leads multiple if-else cases Please, say, maybe i somehow skipped some obvious solution?

Hey, I read this nice article : https://medium.com/androiddevelopers/migrating-from-livedata-to-kotlins-flow-379292f419fb but it made me realize I don't know how to do it in Compose. How does this integrate in a Compose world ?

Hi guys. How do I achieve 45deg angle gradient in compose?

Hello, I’m having this issue when I change between dark/light theme:

java.lang.NullPointerException: Attempt to invoke virtual method 'androidx.navigation.NavDestination$DeepLinkMatch androidx.navigation.NavGraph.matchDeepLink(androidx.navigation.NavDeepLinkRequest)' on a null object reference

my setup is:

setContent {
    val navController = rememberNavController()
    NavHost(navController, startDestination = NavRouting.Home.destination) {
        composable(NavRouting.Home.destination) { ... }
        ...
    }
    navigationManager.commands.collectAsState().value.also { command ->
        if (command.destination.isNotEmpty()) {
            navController.navigate(command.destination) { launchSingleTop = true }
        }
    }
}

Regarding navigation events with

MutableStateFlow

I was inspired by Joe Birch post. What am I doing wrong? 🤔 Thanks.

I'm looking for a way to synchronise scroll between multiple

LazyColumns

. All columns should receive the same scroll delta, regardless of where the user input came from. Is

nestedScroll()

the right thing to use?

Hello All, I'm facing a issue with the StateFlows in composable, for some reason the Stateflow is making the composable re-render infinitely even when there is no update to the value. Below is the code for the same

Do we have an estimated date for a 1.5.0 compatible release?

I have a simple sign-in screen with two TextFields. When I press on either field, the layout scrolls up so that the field is above the Keyboard. So far so good. However, if I request focus with FocusRequester on the TextField (as a result of ImeAction.Next), the cursor moves to the right field, but the layout is not scrolled - the textfield is focused but hidden by keyboard. Any ideas how to cope with that? Compose 1.0.0-beta-06

Hi! I’ve a

Scaffold

with a

BottomAppBar

(because I want the cutoutShape effect) and a few

BottomNavigationItem

(this also happened when I had

BottomNavigation

as a parent instead of

BottomAppBar

) and the problem is there’s no “selected” effect on the menu items. I’ve checked and the var is being changed accordingly, but I see no UI change. To test it I did this (to my

BottomNavigationItem

icon

and

label

):

colorFilter = ColorFilter.tint(MaterialTheme.colors.onBackground.copy(alpha = if (isSelected) 1f else .5f)),

and it works. What am I missing to get this working properly with the

selected

property? Or the selected state is not meant for the item (icon and label)? Thanks

Does

Modifier.zIndex

imply a performance penalty?

beta07 is here: https://developer.android.com/jetpack/androidx/versions/all-channel

Hey my people, if anyone is interested, why isn’t there a more sure way to use this function:

public fun NavGraphBuilder.composable(
    route: String,
    arguments: List<NamedNavArgument> = emptyList(),
    deepLinks: List<NavDeepLink> = emptyList(),
    content: @Composable (NavBackStackEntry) -> Unit
) {

I was recently thinking about a way to make it more sure that all the variables would be more involved in a way that we could assure correct navigation. This came from a colleagues question about “if the route was different than the” called navigation path:

const val toTest = "$TEST/{$TEST_VALUE}"

fun test(testValue: Int) {
    navController.navigate("$TEST/$testValue")
}

Because of this I was thinking if we could have an object that would make this a more sure process. Does it make sense? Is my process incorrect? Accepting suggestions 🙂 My plan now would be to overwrite this NavGraphBuilder.composable function in a way that it would receive this object and that I could use this object instead of this loose variables 🙂

1.0 is announced for July ❤️

Wasn’t beta07 supposed to support kotlin 1.5.0?

e: This version (1.0.0-beta07) of the Compose Compiler requires Kotlin version 1.4.32 but you appear to be using Kotlin version 1.5.0 which is not known to be compatible.  Please fix your configuration (or `suppressKotlinVersionCompatibilityCheck` but don't say I didn't warn you!).

Did I hear this right? Has Compose for Wear OS been open-sourced?

great, Compose beta07 works with ArcticFox beta

There is one exciting update that you won't see in the release notes. Take a look at the new compose-material refdocs, with richer docs and images. Feedback is welcome, as we'll be working on updating the other packages too 🙂 https://developer.android.com/reference/kotlin/androidx/compose/material/package-summary

Android 12 has a new overscroll effect which works out of the box with existing apps. Compose views seem to be an exception though, they don’t get the new effect automatically. Will this require reimplementing the effect in the compose library in an upcoming version? https://developer.android.com/about/versions/12/overscroll

Any indication yet when we'll see Compose available for Wear OS?

AnimatedVisibility(visible = true, initiallyVisible = false, enter = fadeIn()) { //<=beta06

initiallyVisible

is removed in

beta07

@ExperimentalAnimationApi
@Composable
fun AnimatedVisibility(
    visible: Boolean,
    modifier: Modifier = Modifier,
    enter: EnterTransition = fadeIn() + expandIn(),
    exit: ExitTransition = shrinkOut() + fadeOut(),
    content: @Composable() AnimatedVisibilityScope.() -> Unit
) {
    val transition = updateTransition(visible)
    AnimatedEnterExitImpl(transition, { it }, modifier, enter, exit, content)
}

Does this mean screenshot testing is going to be available to compose out of the box?