the GNOME maintainers would’ve ripped a huge fart, sniffed it and said “usecase??” while closing the issue, as they’ve done for years.
This issue was opened in April 2019, over the years listing various use cases and the reply was always “Make a Gnome extension”. Gnome’s Mutter is the only non-edge case Wayland compositor not to support this feature: https://wayland.app/protocols/wlr-layer-shell-unstable-v1#compositor-support (and Cage’s use case is to provide a kiosk, so that feature is probably not supported because of that specific reason and for such very specific cases it’s understandable)
Sebastian needs to look at Apple’s AppKit frameworks.
Pretty much every app specifies its desired settings, which the OS (including the compositor) can override or manage correctly. They’re not a given in the API (see anything that says xWillY in their API pattern).
Further, macOS uses active workspace and auxiliary instead of primary, that works well. Instead of bike shedding the wording this could be discussed in good faith.
Now, I only know mac programming at this level, I don’t know if Wayland is similar, but it looks like there are established patterns for this, and how to deal with same sized displays, and the presentation software examples wanting to use auxiliary display for presentation vs speaker notes.
There’s tons of ways they could’ve approached this instead of simply saying it’s not a valid usecase.
And it’s not how it currently works anyway. I stumbled upon this issue because the games would simple launch on the first enumerated monitor. Not the primary and not the active - the first port on my videocard.
Right, Apple calls this the active workspace which I think makes sense.
I come from Apple land and am settling in to Linux slowly, I don’t know any id the APIs, but I did try to make a Gnome app and found it an unusable stupid situation.
This issue was opened in April 2019, over the years listing various use cases and the reply was always “Make a Gnome extension”. Gnome’s Mutter is the only non-edge case Wayland compositor not to support this feature: https://wayland.app/protocols/wlr-layer-shell-unstable-v1#compositor-support (and Cage’s use case is to provide a kiosk, so that feature is probably not supported because of that specific reason and for such very specific cases it’s understandable)
My pet peeve is this one: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/work_items/179#note_2965559
(and yes, that’s once again our dear friend Sebastian from the screenshot above)
Sebastian needs to look at Apple’s AppKit frameworks.
Pretty much every app specifies its desired settings, which the OS (including the compositor) can override or manage correctly. They’re not a given in the API (see anything that says
xWillYin their API pattern).Further, macOS uses active workspace and auxiliary instead of primary, that works well. Instead of bike shedding the wording this could be discussed in good faith.
Now, I only know mac programming at this level, I don’t know if Wayland is similar, but it looks like there are established patterns for this, and how to deal with same sized displays, and the presentation software examples wanting to use auxiliary display for presentation vs speaker notes.
removes possibility for user to choose
wat?!
I mean. I kinda agree with him :p
If I’m on display2 and launch a game, maybe i wanted it there.
There’s tons of ways they could’ve approached this instead of simply saying it’s not a valid usecase. And it’s not how it currently works anyway. I stumbled upon this issue because the games would simple launch on the first enumerated monitor. Not the primary and not the active - the first port on my videocard.
Right, Apple calls this the active workspace which I think makes sense.
I come from Apple land and am settling in to Linux slowly, I don’t know any id the APIs, but I did try to make a Gnome app and found it an unusable stupid situation.