I'm looking to display a tree structure, but I also need to be able to drag to reorder, and expand/collapse nodes in the tree. I've done some looking and can't seem to find any existing libraries that tick all those boxes. But thought I might poll the channel here to see if there is one I might be missing. If not, anyone have any tips on where to start making my own implementation? Maybe building it on top of LazyColumn?

This is what Im used to! Notice the added ',' after the

modifier = {}

block.

Dialog

seems to ignore the density values in

LocalDensity

for its content. 🧵

Learnt and wrote about

Indication

and

Interaction

Interface today in compose https://medium.com/@anmol.verma4/jetpack-compose-interaction-and-indication-8cfed0e82bcb

I know that Compose team is planning to address the issue with

@Stable

and

@Immutable

stuck inside the

compose.runtime

artifact, but is there some workaround until then? Especially when I cannot use

.aar

because I'm building a small library which I want to be a

.jar

and so no option of simply adding a dependency on

compose.runtime

...

Do we have a way to tell when a sticky header as “stuck” in a LazyLayout?

[Solved] https://link.medium.com/UQzK9RJr6rb. In the linked blog post how do i get the centered item index as soon as an item is centered??. I was looking at pager code and its based on current page offset the index is incremented or decremented.

Few question about bottom sheet. How do you actually use bottom sheet in combination with bottom tab bar? I have multiple bottom sheets that should be presented on different screens where tab bar is visible. Only solution that worked for me so far is this lib https://github.com/oleksandrbalan/modalsheet. I would be happy to see how other solve this issue. Second question is: did someone tried to implement for example that sheet is initially hidden, when press button open it at 65% and then drag to 90 %. I know that it is possible to use half expanded but is there any option like to add snap points to open at 65%? Thx in advance

If I have a

ContentTransform

with

fadeIn()

and `slideOutVertically()`; is it expected that the slideOutVertically should fade out as well? This doesnt make sense to me, is it a bug?

I would like to get the index of the last visible line in case the text in my

Text

composable overflows. I came across

TextLayoutResult.getLineEnd

that seems like it could help me in this case. However, i need to supply the

lineIndex

. How would i go about getting the

lineIndex

of the line that is overflowing?

[FIXED] I am working on a custom Indication in Compose, and listening to Focus changes from my InteractionSource, End result is to have the TextField glowing when in focus(Focus == Assuming the keyboard is open ?) and normal when not in focus. For some reasons my TextField never emits a value of true when keyboard opens for that TextField when clicked.

Androidx Repo is a 💎 and has a lot of android tests and Demos for jetpackcompose Checkout Foundation demo's here https://github.com/androidx/androidx/tree/androidx-main/compose/foundation/foundation/integration-tests/foundation-demos + Foundation Tests https://github.com/androidx/androidx/blob/androidx-main/compose/foundation/foundation/src/androidAndroidTest/kotlin/androidx/compose/foundation/DraggableTest.kt + Material Tests https://github.com/androidx/androidx/blob/androidx-main/compose/material/material/src/androidAndroidTest/kotlin/androidx/compose/material/AlertDialogTest.kt

I hope it's ok to post this here - I published a Compose Multiplatform-based plotting library that, so far, targets Android, Desktop, and web-canvas. I call it Koala Plot and you can try out the web version of the samples served from GitHub pages here. I'm interested to receive any feedback, and in collaborating with others on it going forward.

I face a strange behavior when navigating to another screen (not using any navigation libraries). When I navigate from screen A -> B, it takes 2-4 seconds until B is displayed. In this time screen A is still displayed although the screen has already been disposed according to my logs:

DisposableEffect(Unit) {
        onDispose { Log.e("ScreenA", "Leaving...") } // is logged immediately after call to navigate to screen B but screen A still visible
    }

I would at least expect an empty screen B immediately after this log. Any ideas? EDIT: logs in thread.

Hello, I'm inspecting animation mechanism, but is confused by this invocation. Is this by design? Inside

VectorizedInfiniteRepeatableSpec

, `repetitionStartVelocity`calls `getVelocityFromNanos`with `targetValue = startVelocity`and

initialVelocity = end

. I can't get the meaning out of it. Compose version 1.1.1.

hello guys. I am retrieving a signed-in user from room database with the intention of updating views in compose. how should i store the user? I have tried remember{} but am getting the error:

Required:

MutableState<User.Companion>

Found:

User

var user by  rememberSaveable { mutableStateOf(User) }

val systemUiController = rememberSystemUiController()
SideEffect {
    systemUiController.setStatusBarColor(
        color = PrimaryColor
    )
}

LaunchedEffect(key1 = context){
    viewModel.userResults.collect{ event ->
        when(event){
            is Resource.Success ->{
                  event.data?.let {// user from room database
                     user = it // It throws an error here
                 }
            }
            is Resource.Error ->{
                Toast.makeText(context, event.message, Toast.LENGTH_SHORT).show()
            }
        }

    }

Hi everybody, I'm currently trying to implement a Barcode Scanner for my compose app. I'm using CameraX and Google ML Kit for this use case. Scanning the Codes and getting the values behind it is already working. Now I'd like to mark the position of the currently scanned Barcode within the camera View. I' having trouble implementing this. The barcode has a property with a bounding Box and I think I'd just have to add this as a overlay to the Preview, but I don't know how to do it. Any Ideas?

Hey folks, I am trying to create a collapsible section in a lazy column that can contain (potentially) hundreds of list items. I'd like this section to be expandable and collapsible with change animations. I've seen Google recommend to use

AnimatedVisibility

for hiding list items, but this has a negative potential side effect when that list of hidden items is very large: when you scroll past the collapsed section, the LazyColumn tries to recompose all the hidden items at once and drops frames or potentially freezes. I've filed the issue here: https://issuetracker.google.com/issues/240599812 but am not sure if anyone has any alternatives? For now we've settled on just removing the items from the lazy list when they are not visible, but that breaks our change animations.

issue related to https://kotlinlang.slack.com/archives/CJLTWPH7S/p1659115703829819

👋 Hi Everyone! I have updated my app to target

API level 33

, and as soon as I did that, all of my instrumented tests that use

createComposeRule

no longer work, and fail with an

ActivityNotFoundException

(it’s looking for androidx.test.core.app.InstrumentationActivityInvoker$BootstrapActivity). Has anyone else run into this problem? I can reproduce the issue using the latest stable Android Studio (Chipmunk 2021.2.1 Patch 1), following these steps: 1. Create a New project using the “Empty Compose Activity” template. 2. Add a compose rule to the included

ExampleIntrumentedTest

, like this:

@get:Rule var composerule = createComposeRule()

3. Run the example

useAppContext

test, and note that it passes. 4. Now, in the app module’s build.gradle, update the

compileSdk

and

targetSdk

to use

33

. 5. Run the example

useAppContext

test again, and see that it fails with

ActivityNotFoundException

… Has anyone else found this? How can we fix it? Thanks!

Is there a way to change statusBar/navigationBar colors in a launcherActivity via something in compose? Or is this just something that needs to be done on the Activity level via styles. Currently if I use accompanist when setting up my themes to try and switch the colors you notice initially they default to the MaterialTheme. (which makes sense. My composable theme hasn't been invoked yet) Guess I was wondering if there's a way to apply your compose themes and set those as the source of truth before the activity default theme comes into play? For instance I'd like to set the status/nav bar to transparent on my launcher activity

I have a form UI written in Compose, the user can click a Create button that triggers an object creation that will be stored in a DB. Initially I was constructing the object in the Compose callback for the Create button, but I believe that's something the UI shouldn't be doing, so I moved the logic to the ViewModel, but then I ended up with a function with a lot of parameters, is there a better way to do this? I was thinking of using a state holder that's updated whenever the fields in the form are updated, so when the Create button is clicked I take the data from the state holder and I don't need to pass several parameters to the ViewModel function, but that would require hoisting the state of the TextFields, which I'm not sure if it's desired

I'm repeatedly finding Jetpack Compose-related code documentation to be unclearly written. Here's an example for `SnapshotMutableState`:

A mutable value holder where reads to the value property during the execution of a Composable function, the current RecomposeScope will be subscribed to changes of that value.

This function should ***not*** be used to (re-)launch ongoing tasks in response to callback

events by way of storing callback data in [MutableState] passed to [key1].

Can someone please give an example of this bad use case for

LaunchedEffect

? I want to make sure that I understand this correctly.

Hello all, looking for some help drawing text along an arc drawn in Canvas. Code in replies.

I used view pager to achieve the below ui. I had to hardcode the padding to 142.dp. Is there any other way to achieve this using pager lib.

Does

currentLines

ever get updated from the

onTextLayout

block? Like if you removed everything else.

With accompanist 0.25.0, the permission flow has changed. https://google.github.io/accompanist/permissions/ https://github.com/google/accompanist/commit/a9506584939ed9c79890adaaeb58de01ed0bb823 Now the

permissionRequested

is missing with the goal for a better UX. But doesn’t this take away the possibility to ask for the permission right away? For example in our flow the user clicks on a camera icon. In this case I don’t want to show her a dialog where I explain that I’m now going to ask her for her permission.

Hello guys, I am new in compose and I got the error below when i tried to run my compose project the first time. Please, how do I resolve the error?

Execution failed for task ':app:compileDebugKotlin'.
> Could not resolve all files for configuration ':app:kotlin-extension'.
   > Could not find androidx.compose.compiler:compiler:1.3.0-alpha02.