I'm using

CircularProgressIndicator

and I want to change it's size. When using

Modifier.size(size)

it's getting clipped. Is there any other way to resize or is it not supported yet?

Material has regular input fields and condensed input fields. How do we use condensed text input in compose material?

I found Navigation Compose buggy when i will try to pop the whole stack but it works sometimes. I wish, there is method for clearing the complete back stack, popUpTo is very confusing

My composable has a

LaunchedEffect

(that creates a toast), keying on a state variable (via

by x.collectAsState()

). However, when the state is transient i.e. it changes relatively quickly from state A to state B, the

LaunchedEffect

is not triggered at all for either state A or B. Its a login screen and the user state transitions from a user login error to an anonymous user pretty quickly. I can make some changes to how the state is changed to avoid thus, but I'd like to understand what is going on here.

I’ve upgraded to #compose-desktop 0.4.0-build183 and started getting this error:

e: …/SnakeLayout.kt: (30, 42): Type inference failed. Expected type mismatch: inferred type is @Composable() (Int, T) -> Unit but (Int, T) -> Unit was expected

Code is kinda like this:

fun <T> SnakeLayout(…,
    content: @Composable (Int, T) -> Unit) {
    Layout(…,
        content = { items.forEachIndexed(content) } // here
    ) { … }
}

If I expand the call to

items.forEachIndexed { i, t -> content(i,t) }

it works fine. In version 0.4.0-build180 both variants worked. (posting here, because I believe it is more to do with compiler plugin than desktop lib)

How to manage state for structures like "File System" (Nodes with list of themselves)?

data class Node(
    val name: String,
    val children: List<Node>
)

I want to follow UDF + single source of truth. Level of depth is unknown (assume it's unlimited). How to follow immutability for updates (add/remove node) in this case if i should at all. Maybe it worth to try mutable state, but idk how to cook mutable state with compose and don't break recomposition.

HorizontalPager continues the fling from horizontal LazyRow. This is apparently Expected behavior but it differs from traditional android views and also feels really bad. Anyone knows how to work around it? Relevant github issue: https://github.com/google/accompanist/issues/347#event-4607690257

Hi ! It seems I can't use

WithConstraints

any more (AS reports a syntax error and does not find an alternative, nor purpose an import). What workaround should I use ? My use case is that : • in portrait, one component must take the full client width (the application allocated width), • in landscape, the same component must take the full client height.

How can I toggle a preview in Landscape mode in Android Studio ? (I've got the latest Artic Fox)

I am trying to adapt the design of my Composable between portrait/landscape mode. But I'm always getting the landscape configuration. More in the thread.

Hi Kotliners, I need help on implementing this

I have a problem with the

BottomSheetScaffold

the bottom sheet keeps expanding. It seems like no matter what I do it just keeps popping open. Has anybody else run into this problem?

Is there a way to use

rememberSaveable

with

StateFlow<T>.collectAsState()

? I'd like to keep the state save/restore machinery in the composition if possible.

I have 3 composables need to be laid out in a column. I need one aligned to the top. I need one aligned to the bottom. And I need one in between that takes up the rest of the available space. How would one achieve that? Perhaps the

BoxWithConstraints()

?

Is there any way to get

Application

reference in a composable, just like

LocalContext.current

??

I try to animate a transition between current data state and previous one. I have difficulties to put everything in place in my mind to achieve the transition considering the previous state. I read https://developer.android.com/jetpack/compose/animation but it didn't help so far. I have a 4x4 grid compound of cells. I can move cells in all directions (imagine a 2048-like game). I'd like to do 3 transitions: 1. animate "slide" of tiles 2. animate "transform" of tiles (2 identical tiles are merged together creating a new one with higher value) 3. new tile appearance (one new tile appears at each move) I struggle on how to achieve this…

Seems like my slack thread gets broken with infinite "loading history". Does anyone experienced same stuff or it's problem on my side?

Hi folks, I trying to embed Compose runtime in a project and I'm not getting it to recompose when a state change and updating my tree, what I'm missing? Source: https://github.com/DevSrSouza/compose-tree-test/blob/master/src/main/kotlin/Test.kt

Hi everyone! I'm working in a composable that receives an hour in Unix, UTC ( a Long value like 1608124431 ). I want to check if the next hour the composable receives is before or after the current hour displayed. How could I achieve this? My first approach was trying to remember the last hour but I missed up on how to access the last hour displayed...

Is it possible to make the height of all items in one LazyVerticalGrid row match the largest ones?

Is there a way to add padding to composable content's (direct) children? for example by a modifier? Something like

@Composable
fun Content() {
   Column(Modifier.childPadding(inner = 4.dp)) {
       Text("...")
       Text("...")
       Text("...")
   }
}

when clicking back after bottom sheet collapsed app is crashing. I've used Backhandler present in activity compose lib to collapse the sheet on back click.

java.lang.IllegalArgumentException: The target value must have an associated anchor.
        at androidx.compose.material.SwipeableState$animateTo$$inlined$collect$1.emit(Collect.kt:135)

Hello! If I do

Content(viewStates.collectAsState().value)

@Composable fun Content(state: ViewState) {
  Text(text = state.title)
  Text(text = state.description)
}

Would both Texts be always recomposed even if (for example) there were 5 emissions and in all 5 only title was changing?

we’re partially migrating our Views to Jetpack Compose, when we’re configuring the onclick for button/text, we notice a lags 😞 any references or best practices to smooth the animation when clicking text/button?

most of our code was referenced from official jetpack compose samples

Hi, I have a question relating to matchParentSize / Intrinisic layouts. The use case is i have an accordion looking structure where i click sections to expand them. Alongside this whole structure I want a bar to match the height, including when it expands (more details in thread).

Seems like similar question. Let say i have:

Row{
  LargeComposable{}
  Column{
    SmallComposable()
    ...
    SmallComposable()
  }
}

How can I reach Column height same as LargeComposable height. With ConstraintLayout I use     

height = Dimension.fillToConstraints

I am facing a weird issue where AS can’t understand basic Kotlin features. e.g.

contains(), count()

methods on String and

listOf(), forEach()

methods for collections. Have anyone faced this issue recently?

Where could I start to look, if preview function is broken. It shows only "Initializing...". I'm using AS Canary 14 with embedded JDK and Kotlin 1.5.0-RC plugin installed. Even an new project is broken so it's not project related. Any ideas?

Question about font weight. It is represented by an integer, and the standard weights are increments of 100. This suggests that it should be possible to (somewhat) smoothly animate between weights. However, when I try doing so, at least with the standard system font on a Pixel 3, it looks like the actual weight values are being coerced to a fixed set of weight steps. So it would seem like the weight values are not being used to somehow dynamically draw the weights. It makes sense that the font is just asked to provide glyphs as close as possible to the weight, so I’m not surprised, but just wanted to confirm.