Thomas Adam <tho...@fvwm.org> writes: > On 22 Jun 2016 1:24 a.m., "lee" <l...@yagibdah.de> wrote: >> >> Thomas Adam <tho...@fvwm.org> writes: >> >> > On 10 October 2015 at 11:53, lee <l...@yagibdah.de> wrote: >> >> Hi, >> >> >> >> the subject pretty much says it: >> >> >> >> Can I somehow make it so that fvwm ignores particular windows when >> >> figuring out where to place a new one? >> > >> > Adding a style to ignore windows from placements is the way to go. >> > I'll do this later on. Would be useful with MinoverlapPlacement, for >> > instance. >> >> Oh, that would be awesome! >> >> How do you think about the idea of possibly giving each window a >> stacking priority? It might allow for a more fine-grained control >> across all windows than a style could provide. > > EWMH defines this, and there's Layers.
Which means? EWMH seems to be supposed to make it so that areas of the screen are /not/ covered by windows, which is something I don't want. I'm not sure what layers do other than that they somehow seem to help keeping windows on top. How could they be used to modify the window placement in such a way that a particular window will be covered by others rather than get in the way when another window is placed? I'm using MinOverlapPercentPlacement, after trying MinOverlapPlacement. Both seem to give pretty much the same results. -- After using i3 for a while, I totally realized that it is the job of the window manger to mange the windows, literally. It is, by all means, /not/ the job of the user. Once you realized this, you can see the irony of calling an operating system "Windows", and you even have to say they did a good job with that.
