I have an issue with

SwipeToDismiss

state when navigating back and forth between screens. I would like to

reset

(suspend function) the

dismissState

as part of a cleanup. (Or “forget” that state when navigating back to this screen) Idea: When the user swipes out a Card in a LazyList the card stays in the swiped out state while a SnackBar appears. If the snackbar gets dismissed, the element is deleted via the viewModel. If the snackbar action (Undo) gets pressed, the dismissState gets reset. Problem: If I navigate to another screen, the coroutineScope the snackbar is opened gets cancelled. The dismissState will never be reset. When I navigate back to this screen, the swiped card will stay swiped. I tried but failed: A) Have a

finally

block in the coroutine to do the cleanup. B) Having a

DisposableEffect

seems to not work as I cannot access the compose state and have no coroutine scope. Sourcecode:

edit: in thread

Does anybody know how can I design a layout like this?

What's the right way to have a LazyColumn inside a Column with

verticalScroll

modifier? For example in the Bloom AndroidDevChallenge app home screen.

This might be a dumb quesiton, but in the compose sample for produceState, there is an initial value of Result.Loading, what Result type is being used in the samples that include the .Loading member? I haven't been able to find a Result type to import with that support and want to avoid making a new one if it already exists somewhere produceState: convert non-Compose state into Compose state

@Composable
fun loadNetworkImage(
    url: String,
    imageRepository: ImageRepository
): State<Result<Image>> {

    // Creates a State<T> with Result.Loading as initial value
    // If either `url` or `imageRepository` changes, the running producer
    // will cancel and will be re-launched with the new keys.
    return produceState(initialValue = Result.Loading, url, imageRepository) {

How to find GlanceID for GlanceAppWidget?

I haven’t fully understood why we wrap mutableStateOf with remember. Can someone please explain? Does a mutable state reset to initial value if it’s not wrapped in remember?

Seeing a crash related to compose not finding viewTreeLifecycleOwner, full stack trace in thread

Would

derivedStateOf

be the State-equivalent of

combine

in Flow / Rx-World? Meaning, if one of the inputs change, the resulting state should be recalculated? And can this also safely be used inside a ViewModel? Background: I have e.g. a list and a search bar, and using

MutableStateFlows

inside my ViewModel for data streams. Whenever the search term changes, I

combine

the search term with the list, to filter it. Works well and solid, but I think about going full Compose also in my ViewModels, therefore replacing my

MutableStateFlow

s with Compose States. Is this the correct approach, using

derivedStateOf

?

Is it possible to change the animation when showing a Dialog? Currently when shown it kind of slides in from the left and expands (video and code in thread).

Hello… Is there any workaround to make

BringIntoViewRequester

works in the following situation: 1.

TextField

is at the bottom of the screen and the user tap on it and it gain focus. 2. System keyboard is displayed and the

TextField

becoming visible because of the following:

Modifier.bringIntoViewRequester(bringIntoViewRequester)
.onFocusChanged {
    if (it.isFocused) {
        coroutineScope.launch {
            delay(300)
            bringIntoViewRequester.bringIntoView()
        }
    }
}

3. The user now press the system back key and the keyboard is closed, but the

TextField

still has focus. 4. Finally, if the user tap on the

TextField

again. The keyboard is opened on top of the

TextField

and the

BringIntoViewRequester

is not triggered again because the focus haven’t changed. I know there’s a ticket kinda related to this… https://issuetracker.google.com/u/0/issues/192043120 Any suggestion?

Is there any way to have a degree adjust for a linearGradient?

Brush.linearGradient(listOf()))

My designer keeps giving me stuff like this 😅

background: linear-gradient(180deg, rgba(5, 64, 87, 0.5)

and

background: linear-gradient(215.31deg, rgba(255, 255, 255, 0.1)

Unable to have interaction in Compose Preview Does it not possible to use list ADT e.g:

HashSet

as

remember { mutableStateOf(hashSetOf()) }

See video & snippet code in 🧵

Might sound stupid, but does anyone have any tricks to remembering arrangement vs alignment? I find it to be like plugging in a USB cable... takes at least 2 or 3 tries to guess the one that I want. 😅

Hello, does anyone understand when you should use viewmodel + mutablestateOf() vs. using remember?

Hi , does anyone know why println("hello") will not be called if there is a composable inside the ?.let{}

val name: String? = null
name?.let {
      Box() {

      }
} ?: println("hello")

Is there a way to render the vector icons are in the IDE so I don't have to run my code to check the icon choice?

compose's

setContent

seems to be drawing too much CPU time. Is it natural?

Hello guys, I been trying on compose to have a list view and if an item is selected then I need to make the selected item to move slightly to the right thereby making item drawing outside the lazy Column. How to achieve this? Any idea is welcome. Thanks in advance.

Probably off topic: Does anyone know a dedicated Slack community like this for iOS / SwiftUI related stuff?

I am trying to write some tests for my Compose app but I am getting

Default FirebaseApp is not initialized in this process com.livingmaples.videoplayer.test. Make sure to call FirebaseApp.initializeApp(Context) first.

Does it make sense to cache values of frequently used calculations or extensions, like

.dp

,

RoundedCornerShape

,, etc. in some global space?

// some global .kt file
val cornerShape = RoundedCornerShape(3.dp)
val imageSizeLarge = 120.dp
...

Or does the Compose compiler take care of it, and we are free to reuse those same values all over the place? Or are they so cheap to create that it is even encouraged to write them out each time?

private class PreviewUserInfoProvider : PreviewParameterProvider<UserInfoBean> {
    override val values: Sequence<UserInfoBean>
        get() = sequenceOf(UserInfoBean("111", "111", ""))
}

@Preview(
    name = "user info layout",
    group = "node",
    showBackground = true,
    backgroundColor = 0xffffff
)
@Composable
fun PreviewUserInfo(@PreviewParameter(PreviewUserInfoProvider::class) info: UserInfoBean) {
//    UserInfoView(
//        modifier = Modifier.size(120.dp, 30.dp),
//        userInfoBean = info,
//        onUserClick = {})
    
    Text(text = info.nickName)
}

why it cannot be preview shown?

Compiler behavior question - this crashes:

class Obj(val id: Int) {
    @Composable fun id() = remember { id }
}

// later ...
var obj by remember { mutableStateOf(Obj(0)) }
LaunchedEffect(obj) {
    delay(1000)
    obj = Obj(obj.id + 1)
}
require(obj.id == obj.id())

I understand what's happening and I know how to solve it (use

remember(this)

in Obj, or

key

) but I wonder if this is how it should be. Wouldn't it be desirable that the compiler recognizes

obj

as part of the remember call stack? Since

id()

is a member function, it's pretty clear that if the object changes, the old remember should be invalidated.

How to push FAB when keyboard pop up without setting

windowSoftInputMode="adjustResize"

in manifest because this push all the content not just the FAB?

Why do most animation APIs work pixel-based? and given the fact that units in Android are often given in d.p, what is the best practice for creating accurate animations?

It's safe.

I'd like to get the maximum dimension of a device at app startup, but since that depends on the device's orientation,

BoxWithConstraints

does not look like the right tool for that. For example, on a Pixel 4A,

BoxWithConstraints

(at the top level, not within a

Scaffold

) will give

maxWidth

392.dp and

maxHeight

785.dp in portrait, and

maxWidth

801.dp and

maxHeight

348.dp in landscape. I'd like to know that 801.dp is the max, even if the app starts in portrait. Is there a way to do that? | Edit: Rationale in thread.

Is there a way to have multiple

stickyHeaders

in

LazyColumn

? I mean, I need a behaviour that e.g. 3 stickyHeaders all stick to top, not overlapping and not exchanging one-another

Does anyone know whether you can use

Image

composable when using new

Glance

API to create app wdiget?