Chachako
10/05/2023, 5:10 PMWindow
), the screen below should pause. In traditional Android behavior, the screen behind would enter the onPause
lifecycle and release some resources (for example, every fragment in androidx.fragment
handles these events). However, none of the current Compose navigation frameworks handle these. Why is that? I would greatly appreciate it if someone could point me in the right direction. cheersIan Lake
10/05/2023, 7:03 PMChachako
10/06/2023, 3:29 AMFloatingWindow
?Ian Lake
10/06/2023, 3:34 AMFloatingWindow
is the interface added to destinations that indicate that they, as the name implies, float above the other destinations on the back stack, as explained in the dialog destinations page: https://developer.android.com/guide/navigation/backstack/dialog