how to create a nested graph in navigation?

Is there a way to use stickyHeaders with paging in LazyRow/Columns? Without paging, i can just group the data based on a common property and show a sticky header for each grouped data.

Anyone have any ideas why my icon is always black and not Red?

val collapsedPathData = "M 12 13.17 L 7.41 8.59 L 6 10 L 12 16 L 18 10 L 16.59 8.59 L 12 13.17"
    val collapsedPathNodes = remember { addPathNodes(collapsedPathData) }
    Icon(
        contentDescription = "",
        painter = rememberVectorPainter(24.dp, 24.dp, 24f, 24f,) { _, _ ->
            Path(pathData = collapsedPathNodes, fill = SolidColor(Color.Red),) }
    )

Anyone have idea how to enable window transparency in compose desktop?

Hi everyone. I am issuing one funky stuff with State and LazyColumn. Basically updating list item does not make the UI update right away but only after scrolling.

@Composable
fun Test() {
  var items by remember {
    mutableStateOf(
      mutableListOf(
        1,
        2,
        3,
      )
    )
  }

  LazyColumn {
    items(items) {
      Box(
        modifier = Modifier
          .fillMaxWidth()
          .height(100.dp)
          .clickable {
            val list = items
            list[0] = 6
            items = list // this does not make the list to recompose
            items = mutableListOf(6,2,3) // this does not work either
            items = mutableListOf(6,3,2) // this makes the list to recompose
          },
        contentAlignment = Alignment.Center,
      ) {
        Text(text = it.toString(), fontSize = 50.sp)
      }
    }
  }
}

If you know why or got an idea please let me know. P.S. Compose version is

1.0.0-beta02

Hi All, Facing a crash while using Navigation in Compose

java.lang.IllegalStateException: ViewModelStore should be set before setGraph call

Should we use

SideEffect

for atomicity on operation on local state? The doc is a bit unclear:

SideEffect can be used to apply side effects to objects managed by the composition that are not backed by snapshots so as not to leave those objects in an inconsistent state if the current composition operation fails.

So this applies also to snapshot-backed objects when we need to make atomic change on them, right?

Hello all. I have two fragments and each fragment hosts a composable. I have a Composable defined as seen below

Good day everyone. I’m just playing around with compose and was hoping to get some help with animations. Specifically animating between two composables when state has changed. I’m trying to animate using two

AnimatedVisibility

composables like here to slide in/out the composables My issue is that only the top

AnimatedVisibility

plays the animation. I would like to play them both in parallel so it looks like a seamless sliding in and out transition like a viewPager. Thanks!

Hey folks, we're up to over 3,600 people in this channel! If you would like to post a code snippet or stack trace longer than 4-6 lines, please post a quick description in the main channel here and then post the snippet as a threaded reply to yourself. :thread-please: This helps everyone have their messages seen.

Is there any way to "slow down" animation in compose? I'm trying to slow down my AnimatedVisibility composable with the 3 scale options available in dev options but none of them seem to affect it.

Hi again guys, this is partly a Compose question which is why I am posting here, hoping for the best. Please see details in 🧵

Compose integration question: for teams that use static analysis tools like detekt, etc the introduction of Compose and it’s conventions might violate a lot of rules that come with “vanilla” Kotlin programming, such as long parameter lists, “magic number”s in

dp

declarations, top level constants named in PascalCase etc., that we see used in the Compose source code. Is Compose declarative-tree style programming heralding a new set of coding styles/conventions for Kotlin? Wondering if anyone has had to justify “this is how its done in Compose” with regards to style/convention to their coworkers who may not be too familiar with Compose just yet.

Reposting for better reach : https://kotlinlang.slack.com/archives/C01D6HTPATV/p1616312597091600

is there a way to know the maximum height and maximum width of a Column or (Row)? I just know about BoxWithConstraints

I was given a design to basically create a Container (will try to accomplish this via "slot api") that can accept any component but the background of the container should be 50% of the child that it's hosting. So the container still has to be big enough to fit the child... it's just that they want to create this "offset" effect with the color. Brute force solution in thread:

Please help: I want camerax preview use case to fill the whole size of the screen in compose, I am using a PreviewView in AndroidView and it is not filling the full screen, I tried creating same activity with xml (no compose) and is working as expected ? Or is there a direct way in compose to not use PreviewView() at all to show a preview use case full screen ? In xml I had it

match_parent

for height and width not sure how can achieve that here, it just put black screen top and bottom but preview size remains the same if I do 

Modifier.fillmaxSize()

I encountered pretty weird behaviour while using

infiniteRepetable

: I'm using

tween

as

animation

and while having

durationMillis < 1000*48

(48s) everything works perfectly fine, but while trying to animate with

durationMillis

greater than 48s (which seems super weird), it justs snaps from

initialValue

to

targetValue

. Do you have any idea why is it not working correctly? Am i doing something wrong? Here is super simple

Composable

that allows to reproduce my problem:

@Composable
fun Test() {
    val infTrans = rememberInfiniteTransition()

    val value = infTrans.animateFloat(
        initialValue = 0f, targetValue = 1f, animationSpec = infiniteRepeatable(
            animation = tween(1000 * 60, easing = LinearEasing),
        )
    )

    Text(value.value.toString())
}

I’m developing a number of components for 9-slices scaling of images, like a button, background, etc. Asking community for a good name for this 🙂 Like how would you name a class that holds ImageBitmap and information about left, top, right and bottom sizes to render it?

I have a

LazyVerticalGrid

in a

Column

in a

ComposeView

that’s a child of a

NestedScrollView

and I am getting this:

java.lang.IllegalStateException: Nesting scrollable in the same direction layouts like ScrollableContainer and LazyColumn is not allowed.
...

I have seen a couple of this in here as well, but can’t find any that matches the state of my layout. Please how can I fix this?

Is there a way to add delay to spring animation spec?

Hi, small question regarding

ConstraintLayout

. How can I prevent the text from getting out of bounds as in the screenshot? Constraining the the textend to

parent.end

doesn't seem to work in this case.

It seems that using

State

in

ViewModel

is much simpler than

LiveData

. Should I use

MutableState

in

ViewModel

? Is this correct?

In addition I currently have two interfaces. The first interface has some data, which I have to send when navigating to the next interface. But navigation seems to be unable to pass the object, is my following method correct? If not, what should be the best practice?

How can I draw text where the color transparency depends on the y value? Text() doesn't take a Brush so I can't use a vertical gradient

Do you any materials to better understand how to reach "low level" related to """""view bounds"""""" in the Compose world? I need 2 distinct things • where is the "view" on the Window (I'd like to anchor a dialog to a view) • what is the size of my "view" (≃`View.getMeasuredWidth()` or the value we get from

View.onSizeChanged()

), what is the DPI of the screen where my "view" is (≃`Context.resources.displayMetrics`) → I'm aware there is no such "view" in the 100% Compose world, what I'd like is the have such thing within the layout for the result of a given composable

In this example, the selected text and the highlighting fades with the

Crossfade

, but the "thumbs" do not (they abruptly disappear when the animation ends). Is there something I need to do differently to get them to fade as well?

Hello All! Looking for samples without using ViewModel at all. Since we have Desktop now. Thank you

We have Compose composables in a submodule and have issues with the Preview annotation. Why does @Preview need a "androidx.lifecycle.viewmodel.R$id class?

java.lang.ClassNotFoundException: androidx.lifecycle.viewmodel.R$id

at com.android.tools.idea.rendering.classloading.RenderClassLoader.getNonProjectClassData(RenderClassLoader.java:218)

at com.android.tools.idea.rendering.classloading.RenderClassLoader.loadClassFromNonProjectDependency(RenderClassLoader.java:185)

...

at androidx.lifecycle.ViewTreeViewModelStoreOwner.set(ViewTreeViewModelStoreOwner.java:50)

at androidx.compose.ui.tooling.preview.ComposeViewAdapter.init(ComposeViewAdapter.kt:615)