Hello everyone, I was checking the source code of Material Theme declaration in Compose (alpha11) I realized that the classes :

Colors

and

Typography

are annotated with different annotations

@Stable

for the first and

@Immutable

for the second. Does this mean at a higher level that The Material Theme Composable expect colors to change at a moment of time (dark/light) but not expecting a change of typography ?

Is there any example of Animation between Screens which is Composable? Also i’m not using Compose Navigation. @Doris Liu

hey guys.. is there a way to send an parcelable to compose navigation via

navigate("")

?

hey! About navigation component… I can’t use popUpTo with a String (route) in nav-alpha06/compose-alpha11. If I write popUpTo AS shows both options (the one that accepts id:Int and the one that accepts route:String… but then it only accepts the Int version. And in the NavOptionsBuilder there is only the id:Int version, which makes sense with AS not compiling with a String… How do I use popUpTo with the route?

Is there any way to auto-place the cursor at the end of the already inputted text when the user brings the focus onto the OutLinedTextField?

Hello everyone, Is it possible to perform a transition tween animation for width property which starts from a specific

dp

value and ends with

fillMaxWidth

? For example:

val width = DpPropKey("width")

val transitionDefinition = transitionDefinition<ButtonState> {
    state(ButtonState.COLLAPSED) {
        this[width] = 60.dp
    }
    state(ButtonState.EXPANDED) {
        this[width] = ??? // how can I represent a `fillMaxWidth` value here?
    }
}

Thanks!

Is there a Grid component that is not Lazy(not scrollable)? I found this one but it can’t set Gird Gap. https://github.com/android/compose-samples/blob/2cff65334ea023956a58f215a13b6a55c7[…]ck/app/src/main/java/com/example/jetsnack/ui/components/Grid.kt

Hi all ! Sorry for this long example just in order to explain my main trouble : • I've drawn a checker board with some coins • We can drag a coin to an empty cell • If trying to drag a coin on another coin, then there should be a back animation. Unfortunately, the back animation is not thrown and the coin goes back immediately

Is a

androidx.compose.animation.core.Transition

cheap or expensive to create ? I mean, is it safe to create an array of

Transition

? I mean a 64 cells array

Is it possible to write a Compose UI test that creates some composable UI, then removes it, and assert that the Composable UI isn’t there using the

AndroidComposeTestRule

assertions? Example in thread.

On the debouncing of text fields I have a

BasicTextField

whose

onValueChange

does two things: 1. Feeds `onValueChange`’s value back to the

BasicTextField

to display what the user has typed. 2. Triggers an HTTP search call to fetch updated data to be displayed. I’d like to debounce 2. but not 1. but: since the

onValueChange

is a single callback I see no “easy” way to do it. Were I to debounce the whole

onValueChange

callback, the user will notice a lag with the on screen feedback too. I believe this is a pretty common use case so I’m wondering if there’s a compose friendly pattern to handle this or if something ad-hoc must be concocted.

Hi all, I have a

ScrollableRow

with list of composable. Is there any state within compose that I can use to know if that view has been brought to Foreground (basically I want to know onResume() has been called)? Based on that I can scroll the list to the start.

@Siyamed Is there any way i can know when keyboard is Visible when using BasicTextField ?

I apologize if this has already been asked; has anyone used Compose without an Arch Component

ViewModel

to cache state across configuration changes?

Does being modular mean less decoupling in Jetpack Compose?

Could you help me to understand recomposition? This code adds a different number to

counts

list on each tap. I expect it to render a new

Count

and somehow move previous rows down without calling

Count

again. Is it possible?

@Composable
fun CounterApp() {
    var counts by remember { mutableStateOf(listOf<Int>()) }
    var taps by remember { mutableStateOf(0) }
    Column(
        modifier = Modifier.fillMaxSize().clickable(onClick = {
            counts = listOf(taps) + counts; taps++
        })
    ) { Text("$taps"); Divider(); counts.forEach { Count(it) } }
}

@Composable
fun Count(n: Int) {
    Log.d("Count", "$n")
    Text("$n")
}

Is there any way to use

androidx.paging.compose.LazyPagingItems#getItemCount

for recomposition on change?

I have an unexpected (to me at least) behaviour with

OnDestinationChangedListener

of the Navigation component. I have a bottom nav bar with 3 items, and the third is a subgraph. When I navigate to that one my OnDestinationChangedListener gets called twice, first with the start destination and then with the actual destination. Is this the intended behaviour?

Does

Checkbox

have

onCheckedChange: (Boolean) -> Unit

instead of

onClick: () -> Unit

only to support

TriStateCheckbox

? I can see why it's there for that but if you are not using TriStateCheckbox (the normal usage case?) it seems strange that it's just not onClick (like Button, RadioButton, TextButton, and even TriStateCheckbox itself). Why not have a second signature for CheckBox with onClick instead of onCheckedChange?

Out of curiosity, has anyone ever written a recursive @Composable function?

Is Navigator a good use-case for provided as an Ambient?

If I handle config changes manually (no activity recreation) and I want to override the system language the only way I’ve found is by using

updateConfiguration(config, displayMetrics)

, which works fine but happens to be deprecated 😅. All other ways that I know of rely on activity recreation (wrapping the context and using

createConfigurationContext

, using

attachBaseContext

, using

applyOverrideConfiguration

). Is there a non-deprecated way of doing this (without recreating the activity)? (I think overwriting the language is considered not being the best practice, but it is quite common and many clients want it 🤷‍♂️)

How do I make a composable fill remaining space in a

Column

? Tried

fillMaxHeight

but that takes up the entire column

If I set my

kotlinCompilerExtensionVersion

to

1.4.21-2

should I also set all of the other kotlin versions to the same thing? i.e. kotlin-stdlib, etc? I feel like I never heard about this -2 release of kotlin

This compose doc page has this line, but this setup doc does not. Which doc is right?

freeCompilerArgs += ["-Xallow-jvm-ir-dependencies"]

I copy a `mutableStateListOf` example from docs without any changes, but it doesn't seem to work. AFAIU it should add new names, but the list on the screen stays empty. If I change it to

var names = remember { mutableStateListOf<String>() }

it starts to work. Is it a mistake in docs or am I doing/expecting something wrong?

Someone on StackOverflow is asking a question about button click sounds. I'd like to know the answer too, as I noticed my compose buttons do not make any touch sounds when clicked. Any ideas? https://stackoverflow.com/q/66080018/5513788

The problem with intrinsic size is that currently is not supported for SubcomposeLayout. So is there any other way to match the height of the Divider with the ComposableX?

Hi all! We do have things like

TextField

and

BasicTextField

,

Text

and

BasicText

. But I can't seem to find the "Basic" version of a

Button

. That is - if I don't want to use the material buttons or library, is there a barebone composable for a button or I'd have to implement one myself?