Skip to content

Allow creating LayerMaps and using custom area rather than always output size #1709

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

Open
YaLTeR opened this issue Apr 12, 2025 · 2 comments
Open

Comments

@YaLTeR
Copy link
Contributor

YaLTeR commented Apr 12, 2025

It would be useful to get non_exclusive_zone() only taking into account specific layers. In particular, I'm thinking about "only overlay and top layer" non-exclusive zone: the idea is to render background and bottom layer popups below the top and the overlay layer, so unconstraining them should take into account only the top and the overlay layer surfaces, but not the background and bottom layer surfaces.

@YaLTeR
Copy link
Contributor Author

YaLTeR commented Apr 12, 2025

Hm, I guess this doesn't make much sense unless we also add exclusive zone ordering based on the layer. So e.g. top layers always get laid out before (and thus closer to monitor edges) than any bottom layers. Right now the ordering seems to be based on the order of creating the layer surfaces.

@YaLTeR
Copy link
Contributor Author

YaLTeR commented Apr 26, 2025

After thinking some more about it, I think this is better solved at compositor side by creating and managing separate LayerMaps as necessary rather than one global layer_map_for_output(). Which is not currently possible actually.

@YaLTeR YaLTeR changed the title LayerMap::non_exclusive_zone() but per-layer Allow creating LayerMaps and using custom area rather than always output size Apr 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant