-
Notifications
You must be signed in to change notification settings - Fork 8
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
(Unrelated) How to create a simplest navigation #21
Comments
I removed wrapping layers in remember{} and it works ok, but the whole solution looks hacky and maybe has performance issues as well, can you comment on this? |
Sorry I don't quite understand what you're looking to do here? Are you trying to create your own navigation model? In Guia, you can have a list of your navigation entries, which can be added to a Check out the express lore in the readme. |
im not trying to use guia in any way, just looking for general advice |
Oh, I see, sorry I am not sure of your problem and cannot help you outside the context of this library unfortunately. You are welcome to check out the code, especially the containers being used, there's quite a few things to do in Compose to make sure the "Screens" behave properly, remembering a saved state, lifecycle, etc. |
So i'm working on a project where I'm building a compose navigator which gets composables from outside Composable code
For this purpose the implementation is kept simple:
Maintain a list of objects with a @composable Content( ) function and loop over it in a Box composable.
However it's buggy and removing a layer doesn't remove it from UI for some reasons.
I was looking into how other compose navigation libraries do it but none fit the purpose so I was hoping if you could help me improve this implementation
Here's all the code
I use it like this, I can add multiple layers reacting to app state this way
The text was updated successfully, but these errors were encountered: