New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Navigation] Add mechanism for specifying zOrder in transitions #1001
Comments
How would you expect z-order to be exposed? As a property on each |
I think exposing it (somehow) on the definition of the transition would make sense. In the context of the transition (initial and target) I'd know what ordering I want...That might mean the transition block is no longer an |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
I have the same issue. Having it inside transition definition would work I suppose. Having it for each
|
any idea if this is something being worked on. it would be great to have. |
I think targetContentZIndex should somehow depend on screen index in backstack |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Same issue for me, I just copied AnimatedNavHost and modified like this
And then changed AnimatedContent
|
@SergKlimov Thats cool solution, but sadly, I tried to copy the AnimatedNavHost.kt content to my local package and it wont even compile :) Can you give tip how you do it ? Thanks |
@SergKlimov Never mind, we must also copy file AnimatedComposeNavigator Edit : I cant find visibleBackStack variable, is your AnimatedNavHost have that variable ? |
|
@codingfd thanks |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Maybe it's time to get rid of stale bot? |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Hey @ianhanniballake , I had a try but it's not good. I tried the navigation route: A -> B -> C -> B -> A, when the screen transition running from B -> A, the zIndex looks not good. Could you have a try? |
Sounds like #1411, please follow along there. |
Description
AnimatedContent
supports setting a z-order on the transitions which can be useful for navigation transitions. For example when trying to implement a "slide from bottom" transition, the enter transition slides over the exiting composable (good) but the reverse will slide the exiting (popping) composable under the entering composable. If specifying the z-order could help to explicitly set the desired order for the composables.The text was updated successfully, but these errors were encountered: