Hello, On Sat, Feb 3, 2018 at 5:48 AM, Keith Packard <[email protected]> wrote: > Hrm. This makes me wonder what to do if the auto-listed window is a > direct child of the root and its geometry changes. In that case, the > Compositing Manager wouldn't have enough control over the display as the > window might well fall under some other decorations painted by the > Compositing Manager. I can think of two options: > > 1) Block the geometry change and send an event to the compositing > manager to deal with it. > > 2) Only add non override-redirect windows to the Auto List, and then > assert that the Compositing Manager and Window Manager are the same > X client so that it would naturally receive geometry change requests > by the client. > > 2) seems sufficient to me; it covers the cases we care about most with > no complicated klugery in the X server for now.
Wouldn't this break Compton? AFAIK it only operates as compositor, which is why it's a popular choice among users of tiling WMs such as i3 and awesome. -- Giuseppe "Oblomov" Bilotta _______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
