-
Notifications
You must be signed in to change notification settings - Fork 232
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
Siblings Occupying The Same Area Need Stacked #15
Comments
but how do you get who is over who? ie using a relative layout you have to relay on who is declared before or after? |
After is always higher since it mirrors the default drawing order. We can't detect the actual drawing order since the method isn't exposed, but 99.99% of the time it's ascending from first to last child. |
mmm so we have nothing more than a "almost ever"... Makes sense, even if i think that the Z explosion is more important for looking at childs and view layers, and two siblings are on the same layer (it's borderilne). |
As I see it, it's 10x the code for 2x the benefit. |
Yes, to me, it depends on how do you know gl. Having worked on it a bit i see differently, but your code is perfect right now. |
Currently siblings are always drawn on the same layer. This is actually bad if you have overlapping views as they and their children can draw over each other on the same level.
A second child which overlaps need to be prompted to a layer higher than its sibling (and all its children).
The text was updated successfully, but these errors were encountered: