On Sun 19 Feb 2017 at 10:04:51 -0600, Matthew D. Fuller wrote: > Whether it's best to alter things to "only use EWMH priority stuff if > we didn't set something else ourselves already", or "let EWMH priority > bits relatively adjust what's already set"[1], or some combination, > I'm not sure. Olaf is the one with all the EWMH knowledge; I strive > to maintain my blissful ignorance of the details :)
Both of those approaches are certainly possible. I tried to keep the EWMH stuff relatively separate from the rest, so any policy that we think makes sense should be doable. Maybe the most practical approach is "whenever the config file says something about stacking, translate it to EWMH stuff and add the appropriate property to the window". Then after that, one just looks at the EWMH property to decide what to do. A refinement of this could be to have "default" and "override" settings in the config file. With icons we already have something a bit like that, with the ForceIcons keyword. The "default" setting gets overridden by the attributes of the window as set by the client, which in turn gets overridden by the "override" settings. That is, unfortunately, more complex. -Olaf. -- ___ Olaf 'Rhialto' Seibert -- Wayland: Those who don't understand X \X/ rhialto/at/xs4all.nl -- are condemned to reinvent it. Poorly.
signature.asc
Description: PGP signature
