For what it is worth I created a windowrolerule <https://github.com/bakkeby/patches/blob/master/dwm/dwm-windowrolerule-6.2.diff> patch a while ago that lets you apply rules based on the WM_WINDOW_ROLE string.
One would typically use something like this to avoid having browser preferences windows, etc., from being tiled. This may be a hit or miss though as you do rely on the application actually setting this role for the popup window. The slight annoying thing is that you have to find these first, then set up rules for every application that you use that has such preferences windows or otherwise. Personally I think that it makes more sense to make all these windows floating by default (as per the original patch), except that it would be better to handle this before rules get applied so that you have the option of preventing windows from being floating if you explicitly do not want it. Best regards, -Stein On Thu, May 14, 2020 at 2:15 PM Jakub Leszczak <[email protected]> wrote: > Just to clarify. I don't mean "example" diff as the final thing that > should be a part of mainline. It is just a draft so you could take a > look and let me know if this is a direction you would like to go with. > Since like I wrote applyrules() is not run on propertynotify() like > updatewindowtype() is. So it is not clear if such patch is a step in > right direction. > > Br, > Jakub Leszczak > > -- Stein Gunnar Bakkeby OpenBet Developer [email protected]
