Re: _NET_FRAME_EXTENTS and window borders

[Sam Spilsbury <smspillaz gmail com>]

Hi Uli,

[0] says "widths of the respective borders added by the Window Manager". _FRAME_EXTENTS is generally used for placement purposes, so I'd assume that includes the border attribute, since the border of the frame window will be visible to the user. I know that Compiz uses the frame geometry offsets + border attribute in calculating placement and tiling, for instance.

I suspect your use case might be more straightforward if the actual size of the parent window was set, instead of relying on the border attribute.

[0] http://standards.freedesktop.org/wm-spec/wm-spec-latest.html#idm140200472552416

On Thu, Aug 27, 2015 at 2:17 AM, Uli Schlachter <psychon znc in> wrote:

Hi everyone,

I am writing because of the following bug report:

  https://github.com/awesomeWM/awesome/issues/425

The problem boils down to the following question:

If a reparenting WM has a non-zero border width (in the XConfigureWindow sense),
should that border be included in the values of _NET_FRAME_EXTENTS?

For a concrete example, let's assume a client window of size WxH. The WM
reparents this window into a window of the same size and sets the border width
of the frame window to 10. Should _NET_FRAME_EXTENTS be set to "0,0,0,0" or to
"10,10,10,10"?

Also, does it make sense to clarify this in the spec, or am I just missing
something obvious? Is there someone who has the knowledge and time to write a patch?

Thanks a lot,
Uli
--
If you have to type the letters "A-E-S" into your source code, you're doing it
wrong.
_______________________________________________
wm-spec-list mailing list
wm-spec-list gnome org
https://mail.gnome.org/mailman/listinfo/wm-spec-list

--

Sam Spilsbury