I have a logic to show animated composable sliding in from top. I was wondering if there's a better ...

# compose

[ritesh]

I have a logic to show animated composable sliding in from top. I was wondering if there's a better way to achieve what i have, the Side-effect part?
More in 🧵

[ritesh]

@Composable
fun MyComposable(somCondn:Boolean){
 var show by remember { mutableStateOf(false) }
 ComposableWhichAnimatesFromTop(show = show) // slides in from top 
 if(somCondn){
       LaunchedEffect(Unit) { // is there a better of doing this, Considering MyComposable can be called on every button click
        try {
          if (!show) {
            show = true
            delay(3000L)
          }
        } catch (ex: Exception) {
          show = false
        } finally {
          show = false
        }
      } 
 } else {
    // Show Loading
 }
}

[Chris Sinco [G]]

Do you want the slide in every time this Composable enters composition? Would also be helpful to see a video of the desired effect

[ritesh]

It's working the way i want, no i do-not want to slide in every-time.
Considering a scenario where, on every button click somCondn is false to showLoading (the else block) and then it's true to show network-error.

[ritesh]

Sharing the video in a while

[ritesh]

rec.mp4

[ritesh]

It's working the way i want

if(somCondn){
       LaunchedEffect(Unit) { // is there a better of doing this, Considering MyComposable can be called on every button click
        try {
          if (!show) {
            show = true
            delay(3000L)
          }
        } catch (ex: Exception) {
          show = false
        } finally {
          show = false
        }
      } 
 }

every time LaunchedEffect enter composition, it checks for the show flag, so there will be no multiple slide-ins.
every time LaunchedEffect leaves or finishes it will make it false.

[ritesh]

I was wondering, if there's a better way of doing it in effect-handler world, if i could avoid try catch and finally

[Chris Sinco [G]]

Have you also looked at AnimatedVisibility? Also curious if the try/catch is for Network exceptions?

[Chris Sinco [G]]

I would actually pull the try/catch Network exception out of the Composable so it's not tightly coupled with this notification component. Then use a Boolean and/or Exception state to track whether to continue showing the notification or not (reduces need to recompose and show, and the animation is more likely to run once).

[ritesh]

I had added try/catch/finally block for cases when my LaunchedEffect gets cancelled in between (catch block) or completed successfully (finally block).
It can just be try {} finally {} block and drop catch {} as in the end i am just making the show=false to slide it up.

[Chris Sinco [G]]

I see. You could try the AnimatedVisibility API then which you can pass show as the targetState then define different animations when entering versus exiting e.g. sliding in versus sliding out

[ritesh]

yeah, MyComposable will be always part of view-tree and ComposableWhichAnimatesFromTop(show = show) does takes the show as param and it internally uses AnimatedVisibility
Sorry, if i was not clear before and thanks for bearing with me!

Thanks Chris.

[Chris Sinco [G]]

I see - I'm still not sure why the try/catch is in your LaunchedEffect if it's only controlling animation, but you may know better. What you could also do is control how you respond on the button click to filter out clicks / not respond to them if you know things are in a certain state.