This message was deleted.

Hello, I want the composables inside the column to have a height min, in addition to using weight for scrollable in small size screen, but when chaining them in the modifier, the height min does not work and is not applied. Do you have a solution for this problem?

So, I know there is the intent that the compose compiler will no longer need to directly line up with the version of compose you are using in your code. Does anyone know of the 1.3.0 compiler makes that possible or not? We’re in the process of getting ready to update our kotlin to 1.7 and compose to 1.2, and i want to be able to decide if we should be using kotlin 1.7.0 (compose compiler 1.2.0) or kotlin 1.7.10 (compose compiler 1.3.0)

I have a vague memory that it used to be possible to have a composable as an extension function, but now I get a warning that it's not(might've never worked). Here's a sample situation of what I naively want:

@Composable LazyGridScope.myFun() = ...

Is there a workaround or suggested solution for this? I guess I can pass it as a param and run

scope.apply{}

.

Weird thing I noticed: I can’t import both

LazyListScope.items

and

LazyGridScope.items

. I’m not sure if that’s intentional or if I’m meant to alias them somehow.

I'm trying to put together a calendar header that scrolls like shown. I can get static versions working, but haven't been able to figure out the magic for doing it with animation. i tried to do a 3 row column with up arrow, weekday row, and down arrow, and then message with the Modifier.offset(y) values, but that doesn't seem to create this effect. Any pointers on how I should go about this?

Does anyone have a good example of using BottomNav with mix of different tabs that wrap native Fragment (that has network calls before showing data) or WebView that allow caching of the tabs so when you transition to a different tab and return the content is shown without reloading?

Is there a less verbose way of writing this?

val lifecycle = LocalLifecycleOwner.current.lifecycle
DisposableEffect(lifecycle) {
  val observer = LifecycleEventObserver { _, event ->
    if (event == Lifecycle.Event.ON_RESUME) {
      vm.doThing()
    }
  }
  lifecycle.addObserver(observer)
  onDispose { lifecycle.removeObserver(observer) }
}

Hi! I just added

androidx.compose.runtime

(with NO other changes to the code base and NO extra added dependencies) to my app and enabled the compose compiler and suddenly pressing the back button from one fragment doesn't allow the fragment it's going back to to load properly... is this a known bug?

(I've updated all my dependencies to the most recent stable version -- including the navigation component)

One of the biggest downsides of Compose for me is the performance. Eventhough I have R8 enabled and I’m running in release build (which is also a downside cause it takes hours to build and heats up my laptop) it is still a poor experience. HorizontalPager + LazyVerticalGrid with 3 columns = 10 FPS Same setup on XML = extremely fast.

How I can pass the click event from child composable to its parent? e.g:

Card(
  Modifier.clickable { doSomething() }
){
   CheckBox(
     .....,
     onCheckedChange = {  } // leave it empty and pass its event to parent
   )
   Text("Some label")
}

Hello folks, A Collection of major Jetpack compose UI components which are commonly used. Hope this will help for the learning. Kindly hit a star if you liked it too: https://github.com/SimformSolutionsPvtLtd/SSComposeCookBook/

hi everybody, I’ve got a problem with a LazyColumn of elements that have a favourite button: basically when I tap the favourite button, the item that is being favourited (a document in my case) is changed in the underlying data structure in the VM, but the view isn’t updated, so I never see any change in the button state 🧵

Hi everyone, I was going through the Jetpack Now In Android official sample. Really great sample but I couldn't find any example of navigation triggered by ViewModel there. In my apps I use Channels to send navigation events from ViewModel but Google seems to be recommending against this approach. I have gone through a lot of official samples but haven't found one which demonstrates how to handle navigation triggered by ViewModel. Does anyone know of any such sample (official or unofficial)? Maybe @Manuel Vivo

I noticed that the M3

ColorScheme

is annotated with

@Stable

, however, it does not override

equals

. The

@Stable

annotation mentions that the following must be true:

1. The result of

equals

will always return the same result for the same two instances.

I assume this means that two instances of a class with the same internal values should evaluate to

true

using

equals

. However, this is not the case for

ColorScheme

. Am I misunderstanding what this means?

Would it be possible to define different screen transition for same route? For example with deeplink i want to have bottom sheet behaviour and if going from screen A to B i want to have push stack behaviour?

Hey yall, has anyone used AndroidView to inflate a PlayerView and use exoplayer to play a video, but backgrounding the app and foregrounding the app seems to make that view disappear. I’ve tried to observe the lifecycle to make sure to only release exoplayer when the lifecycle is destroyed, but this doesnt work, I have logs in the

update

parameter and

factory

parameter and they dont show up when i background the app and then foreground it

I display a non dismissable dialog when the user lost connection. Somehow it’s not working correctly, sometimes the dialog shows up eventhough I’m connected to internet and doesnt want to diassapear. The setup is super easy but still not working. Code in thread

Hey all , Can anyone help how to draw a curved dashed line with arrow in compose. (Similar to the below attached image)

Does anyone have a solution for this problem?

In the project, I just joined I found strange

@Composable

usage

class SomeViewModel(
    repository: SomeRepository,
) : ViewModel() {

    val something: State<String?>
        @Composable
        get() = repository.something.collectAsState()
}

what could be the implication of including

ViewModel

in composition?

How can the parent composable communicate events to the child composable? For example, I want to scroll-to-top the start destination when the bottom bar is tapped.

Are there any APIs in compose text to change a text which spans let’s say two lines to look more “balanced” by making the lines take roughly the equal amount of space? I’m betting on “no”, but doesn’t hurt to ask 😄 Like instead of: Lorem ipsum dolor sit amet consectetur adipiscing elit Do: Lorem ipsum dolor sit amet consectetur adipiscing elit

AnimatedContent

This is the way :mandalorian: https://developer.android.com/jetpack/compose/animation#animatedcontent You could start with default:

AnimatedContent(targetState = loginUiState) { state ->
   when (state) {
     is LoginEmailUiState ->
        LoginEmailPassContainer(state)
     is ResetPasswordUiState ->
        ResetPasswordContainer(state)
   }
}

And then tweak

transitionSpec

as needed, see docs above ☝️

Is there any way to add a Floating context menu with Compose?

Hi guys, Jetpack compose is very easy but not very satisfying in terms of performance. Especially lazylayout so laggy. I tried the suggested methods. I activated R8, got build in release mode. But it still hangs. I wonder if I should switch to xml? What do you recommend ?

Any way to have a

lineSpacing

in

TextField

except using

TextStyle.ineHeight

(lineHeight also changes the cursor size)

I have a weird issue with manual scroll invoking.

LazyListState.animateScrollToItem(0)

suspends indefinitely whenever I intercept the scroll animation by touching the list. Thus blocking the collection for any consecutive animations. Tried working around with

withTimeout

, but it seems like the

animateScrollToItem

animation loop has no way of supporting cancellation (no

yield

in the

while

loop).