Re: _NET_FRAME_EXTENTS and window borders

--===============0667711780174705496==
Content-Type: multipart/alternative; boundary=001a1134612cc6ea0d051e47526c

--001a1134612cc6ea0d051e47526c
Content-Type: text/plain; charset=UTF-8

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 <[email protected]> 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
> [email protected]
> https://mail.gnome.org/mailman/listinfo/wm-spec-list
>



-- 
Sam Spilsbury

--001a1134612cc6ea0d051e47526c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Uli,<div><br></div><div>[0] says &quot;widths of the re=
spective borders added by the Window Manager&quot;. _FRAME_EXTENTS is gener=
ally used for placement purposes, so I&#39;d assume that includes the borde=
r attribute, since the border of the frame window will be visible to the us=
er. I know that Compiz uses the frame geometry offsets + border attribute i=
n calculating placement and tiling, for instance.</div><div><br></div><div>=
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.</di=
v><div><br></div><div><br></div><div>[0] <a href=3D"http://standards.freede=
sktop.org/wm-spec/wm-spec-latest.html#idm140200472552416">http://standards.=
freedesktop.org/wm-spec/wm-spec-latest.html#idm140200472552416</a><br></div=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Au=
g 27, 2015 at 2:17 AM, Uli Schlachter <span dir=3D"ltr">&lt;<a href=3D"mail=
to:[email protected]" target=3D"_blank">[email protected]</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">Hi everyone,<br>
<br>
I am writing because of the following bug report:<br>
<br>
=C2=A0 <a href=3D"https://github.com/awesomeWM/awesome/issues/425" rel=3D"n=
oreferrer" target=3D"_blank">https://github.com/awesomeWM/awesome/issues/42=
5</a><br>
<br>
The problem boils down to the following question:<br>
<br>
If a reparenting WM has a non-zero border width (in the XConfigureWindow se=
nse),<br>
should that border be included in the values of _NET_FRAME_EXTENTS?<br>
<br>
For a concrete example, let&#39;s assume a client window of size WxH. The W=
M<br>
reparents this window into a window of the same size and sets the border wi=
dth<br>
of the frame window to 10. Should _NET_FRAME_EXTENTS be set to &quot;0,0,0,=
0&quot; or to<br>
&quot;10,10,10,10&quot;?<br>
<br>
Also, does it make sense to clarify this in the spec, or am I just missing<=
br>
something obvious? Is there someone who has the knowledge and time to write=
 a patch?<br>
<br>
Thanks a lot,<br>
Uli<br>
<span class=3D"HOEnZb"><font color=3D"#888888">--<br>
If you have to type the letters &quot;A-E-S&quot; into your source code, yo=
u&#39;re doing it<br>
wrong.<br>
_______________________________________________<br>
wm-spec-list mailing list<br>
<a href=3D"mailto:[email protected]">[email protected]</a><br>
<a href=3D"https://mail.gnome.org/mailman/listinfo/wm-spec-list" rel=3D"nor=
eferrer" target=3D"_blank">https://mail.gnome.org/mailman/listinfo/wm-spec-=
list</a><br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r><div class=3D"gmail_signature">Sam Spilsbury</div>
</div>

--001a1134612cc6ea0d051e47526c--

--===============0667711780174705496==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
wm-spec-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/wm-spec-list

--===============0667711780174705496==--