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
Subsurface ordering #2491
base: main
Are you sure you want to change the base?
Subsurface ordering #2491
Conversation
I will gladly take on the challenge. Depending on our plans in Ubuntu Touch this might mean either backporting & refining on top of Mir 1.8 or taking 2.x as is and reporting back This is more or less a requirement for supporting proper stacking of surfaces in multi-window mode in Waydroid, the Android compatibility solution for GNU/Linux systems. |
Hi @fredldotme, got any updates on this? |
Fixes #345. |
Just came around to notify I intend to take a look as soon as my lunar dev environment on my M1 is properly functioning. The idea is to test Waydroid on that configuration soon since I wouldn't have to backport anything really. |
This has been around 9 months, but still "Some checks haven’t completed yet"! I wonder why? |
d2c622f
to
b714cac
Compare
Because the set of required checks has changed since. I've rebased so it gets refreshed. |
Codecov Report
@@ Coverage Diff @@
## main #2491 +/- ##
=======================================
Coverage 78.36% 78.37%
=======================================
Files 1054 1054
Lines 72041 72068 +27
=======================================
+ Hits 56457 56481 +24
- Misses 15584 15587 +3
... and 3 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Attempt at implementing subsurface re-ordering. This should work but I have no way to test. The WLCS tests that failed before still fail, but I don't trust that they're correct. I'm not going to put more work into getting this merged at this time, but if anyone wants to push this feature through this might be a good starting point.
Possibly fixes #2487.