how can I clear compose navigation

BackStack

?

Anyone know how to get the latest kotlin 1.4.31?

What is the best way to load a bitmap with a suspend function? I want to use Google Places sdk and it provide a

Task

that returns

Bitmap

... I've added an

await()

method to convert it to Bitmap directly... but, how to load it onto Composable?

Any idea - why this occurs ? - java.lang.IllegalArgumentException: Layer is redrawn for LayoutNode in state NeedsRelayout [LayoutNode@ef9e093 children: 1 measurePolicy: androidx.compose.ui.layout.SubcomposeLayoutState$createMeasurePolicy$1@2d98fc5]

Should we be using something other than

AppCompatActivity

? It's what's in the default when creating a new compose

Don’t know if this is the right place to discuss but my Compose project is telling me to remove

jcenter

but when i do, all hell breaks loose and i can no longer compile

Does anyone know if

navigation-compose

ever added transitions? Trying to catch up on the last several versions but I didn’t see anything in the release notes, and I swear there was an issue about it but nothing related in the issue tracker: https://issuetracker.google.com/issues?q=componentid:409828

Some questions around

navigation-compose

and ViewModels. For a time now, we've been able to get a viewmodel scoped to a backstack entry (at first by rolling our own factory, then using a HiltViewModelFactory, and now by using

hiltNavGraphViewModel()

). I presume that means that as long as the backstack entry exists, then the VeiwModel will hang around, and won't be cleared until the backstack entry is popped, right? And if so, you might need to be careful in some cases when launching a coroutine using

viewModelScope.launch

, right? If your are just making a newtork call to fetch a piece of data or something, no big deal. But if it's a longer running operation, then it will not get canceled until the backstackentry is popped from the stack. So, if say you have Composables A, B, and C that are entries in your graph, and you navigate from A to B to C ... if the ViewModel for A launched a coroutine in its

viewModelScope

, it will still be running while the user is looking at C, correct? So if your intention is to launch a coroutine when the user is looking at A and have it get canceled when the user navigates to B, then you really need to use a different mechanism (like say

LaunchedEffect

). Do I have that right?

Getting

Fatal Exception: java.lang.IllegalStateException: LayoutCoordinate operations are only valid when isAttached is true

from firebase in my app and not sure what was the issue since I may not able to create a reproduce sample, full stacktrace in thread

Style issue regarding lazy lists. In my lazy lists (e.g.

LazyColumn()

), I sometimes want to extract several items in a function. So I define

fun LazyListScope.FooSection(...) { items....  }

and use it in my lazy lists

LazyColumn { FooSection(...) }

However Android Studio complains the naming since

FooSection

is not a composable, I am wondering if this is not something I should do at the first place.

Now that Jetpack Compose is in Beta and I get lint errors about `Composable functions that return Unit should start with an uppercase letter`I am slowly starting to realize, after months of denial, the battle for lowercase + camelCase for function names (as per the kotlin coding conventions ) battle is over and lost. I just wanted to vent (I am now refactoring the names of the functions in my code for the upper case start) that it looks weird that within composable functions it looks like I am instantiating a bunch of objects instead of calling actual functions. For all the other rebels that share this thought, I want to give the opportunity to press

F

to pay your respects to this fallen topic, and move on to the world of uppercase CamelCase function naming with me.

I am trying to display an image with jetpack compose… which is a normal PNG file inside drawable directory:

…res/drawable-xxxhdpi/ic_test.png

the code I use:

Image(painter = painterResource(id = R.drawable.ic_test), contentDescription = "Test")

produces this exception:

java.lang.IllegalArgumentException: Only VectorDrawables and rasterized asset types are supported ex. PNG, JPG

What am I doing wrong?

I am wondering if canvas drawing should be used for simple shapes if you can use Compose instead. Let’s assume I want to draw Bar Chart. This can be achieved with drawOnCanvas, but also using just Compose Boxes. Furthermore, if BarChart will be very wide and horizontally scrollable, in Compose I could use LazyRow which is not a case for Canvas. What you guys think?

Is there a good way to declare a text with a clickable link in Compose yet?

Is there a compose equivalent to

android:keepScreenOn

?

Any one tried constraintlayout-compose alpha04? It seems it broke some existing layouts. I can’t find any release notes though, can someone point me to them?

Did anyone saw strange FloatingButton animation in newest compose release? In

Scaffold

it’s like animating from left to right after update. How to disable it? 🙂 It’s lagging on emulator

It seems that in beta02 if I add

uiMode

to

android:configChanges

of the activity, the app will only react to the first dark mode change. Just want to make sure I'm not missing anything.

Is there way to increase the duration of

AnimatedVisibility

? I want to slow the animation a bit.

Hi all, I am trying to dynamically adjust the space between the components in my content depending on the visible screen height (keyboard up or not). My content consists of multiple components that are optional, so it could be somewhere between 2 to 10 components. I Don't want to change the height of my components, but only the space between them. So, I would like to have something like min and max height for the spacers in between, so that max height is used when the screen has it. Then it should start to shrink the height slowly as necessary until it reaches min value. Then it should start to scroll after reaching the min value. I am trying to solve 2 problems here; 1. When the keyboard is up. 2. Phones with smaller screens. Any suggestions please..

How do you guys handle complex composables with many parameters? I can combine the value parameters to a state object (which generates more boilerplate code), but I'm unsure what to do if the user can do a lot of stuff. E.g. I have tons of callback methods to pass events to my ViewModel. Also define an Interface with all the possible methods?

Does anyone know how to pass arguments to the start destination of a nested graph?

Hello, everyone! 👋 I published an article with some ideas for handling state between the Composable and ViewModel, based on some conversations with @Adam Powell. I hope that this content can help you the way that helped me. 😊 Thanks a lot! ❤️ https://proandroiddev.com/better-handling-states-between-viewmodel-and-composable-7ca14af379cb

I'd like to do a

Crossfade

on a

Text

when it is set to the empty string, but not when it is updated in any other way. This code will crossfade for every update to the state 'text'

Crossfade(targetState = text, animationSpec = tween(1000)) { newText ->
    Text(text = newText)
}

but I'd only like it to apply when 'text' is cleared. Is it possible to do this with Crossfade, or do I need some other animation mechanism? (I didn't expect using

if (text.isEmpty())

with a crossfaded Text in the

if

and just a Text in the

else

to work, but I tried it anyway and it didn't.)

Tried looking at cs.android.com, but I wasn't able to find if there's a Compose implementation of "Autosizing TextViews" from XML land. Is this possible at the moment?

Does compose have native date/time pickers ? Google results reference a library atm

By using the search function I can't find anything about

Shared Preferences

. Just the hint, that it's not the right data storage solution. I would like to save some settings. What's the right way to store such data persistently?

I think Crossfade should not clip graphicsLayer. When crossfade is animating, it uses:

keys.mapTo(items) { key ->
    CrossfadeAnimationItem(key) {
        val alpha by transition.animateFloat(
            transitionSpec = { animationSpec }
        ) { if (it == key) 1f else 0f }
        // NOTICE
        Box(Modifier.alpha(alpha = alpha)) {
            content(key)
        }
    }
}

And if it is not animating, it uses:

Box(modifier) {
    items.fastForEach {
        key(it.key) {
            it.content()
        }
    }
}

The problem is, 

Modifier.alpha()

  is an alias of 

graphicsLayer(alpha = alpha, clip = true)

 , If you are holding a Button, Card or anything with shadow, Crossfade will clip the shadow when animation starts, and resume when animation finishes, that will be very unnatural. And I wonder the reason that 

Modifier.alpha()

 sets 

clip

 property to true, is that really necessary?