A long introduction to Kotlin Coroutines
The basics of Coroutines, the major building blocks, and a simple overview of the framework
Disclaimer: if you’re new to Android, you’ll most likely have to go through some basics first to understand the catch presented here. If you have some experience already, here’s an interesting question for you:
Does changing visibility on a ViewGroup set the same visibility to all of its children?
The short answer: at the time of writing this post, no.
Let’s imagine that you have a View container, e.g. a
FrameLayout. And now you have a View inside, doesn’t matter which one. You want to hide the container from the screen. That’s easy, right? Just call
setVisibility(GONE) on it and you’re done.
Now imagine you have a custom-built View that reacts to visibility changes. In this custom View, you simply override the
setVisibility() method and you’re done. Now you’re able to react to visibility changes, and do whatever you need to do at that point (for example: stop an animation).
Next, your custom view is inside the View container from above. Setting visibility on the container will not trigger a visibility change on its children – therefore your animation would still keep running. The final effect on the UI may be the same – the container and its child Views are not visible to the user anymore – but technically speaking, you didn’t make any changes to the child views (and therefore didn’t react properly).
This happens both from Java and XML.
People have already asked about this behavior here, and there are some explanations offered, so the link may be worth checking out.
To go deeper, you can check out the LayoutInflater’s source and follow the recursive child inflation sequence. You can then check out the interesting “snapshot” method on the ViewGroup class, or take a look at the original visibility implementation on the View class. All of this confirms my earlier statement.
The problem is especially problematic if you’re stopping animations on
setVisibility(GONE), because animations tend to reset visibility to
VISIBLE on animation loop restart.
To conclude, this behavior is intentional. You can easily work around it only by overriding the ViewGroup class’ behavior, and then setting the visibility to children manually for your custom View containers.
Watch out for the performance hit this introduces during the measure/layout sequence though.