Re: Re: WM_NAME vs. _NET_WM_NAME

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--===============0632682380851679968==
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=_mehl.schokokeks.org-3896-1414402860-0001-2"
Content-Disposition: inline

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_mehl.schokokeks.org-3896-1414402860-0001-2
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Martin Gr=E4=DFlin <[email protected]> [2014-10-27 10:26:14 +0100]:
> > > > It seems the Qt toolkit only sets _NET_WM_NAME and doesn't set WM_N=
AME
> > > > at all. Now that raises some questions:
> > > >=20
> > > > - Should a client also set WM_NAME when setting _NET_WM_NAME? Sure,
> > > >=20
> > > >   it's a good idea for backwards-compatiblity, but is it warranted =
to
> > > >   open a bug against Qt? (I'd say yes, but I'd like to hear other
> > > >   opinions).
> > >=20
> > > From my reading of the relevant section in ICCCM (4.1.2.1) there is no
> > > indication that a client is supposed to set it. Given that it's certa=
inly
> > > not a bug on Qt's side. If a window manager has problems with it, it's
> > > more because the window manager doesn't support EWMH.
> >=20
> > Okay. I'll still open a bug in Qt then since it seems to raise
> > problems in the wild - then it's up to them to decide whether it's
> > worth to fix it or not ;)
>=20
> Fair enough, though I think it's not the task of a toolkit to be bug-to-b=
ug=20
> compatible with each window manager ;-)

Sure, but since it lead to problems in two applications already
(KeePass and herbstluftwm), and everything else (tm) seems to set
both, it still (IMHO) is Qt's job to do it the way it causes the least
friction everywhere else. Of course it'd be ideal if everything else
would support _NET_WM_NAME (and I'll open a bugreport against KeePass
as well), but that's simply not the case.

But as said, that's left to the Qt people to decide then ;)

> > > Shameless plug: as you are using Qt 5, consider using KF5::WindowSyst=
em
> > > which is a nice Qt 5 (only, no further KDE dependencies) library
> > > implementing EWMH, supporting fallback to ICCCM if needed. It's the
> > > library powering KWin and Plasma (e.g. taskmanager) and also used in
> > > LXQt.
> >=20
> > Probably not an option with PyQt, and also that's not really a
> > dependency I want to have just to set a window title :D
>=20
> ah that be more for the case of reading the window title.

That part is in KeePass (a password manager which can autofill fields
in a browser it finds via the title), I just happened to get the bug
report because it works everywhere else :P

Thanks again for your insights!

Florian

--=20
http://www.the-compiler.org | [email protected] (Mail/XMPP)
             GPG 0xFD55A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/

--=_mehl.schokokeks.org-3896-1414402860-0001-2
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJUThMqAAoJEJFusMj9VaBy8qkP/0+4puDD9nnqdiXiWaim/6Dg
DaGRaQCEaUqm5sgkdXQdBElgJkEJgS7mxRW2QcCuNsTzl7fsunn/xEZr/y/tXTi0
0Vf0fKuLW5a9I8Tl+HwWD7zafvOExP7+T5smZtorK0RPuAJcJrwW4JS0KQF5qCzA
LkQvW2xJ26e2u66YzwQG9t6lPkX4p8ffjFLFdrJineFau9awaS2oXZhYSpPvQEq4
VAHKCqG8xHW1R68QwI4LbbRaD2IsDp6dZ3QSgJE6c7gNNByXE1BMocr0e4n5mEcc
P2I9iryTflMbaom2igNXU4k7JxV+GDcFlZYXg0gfrfvpDpHZz93k9TjLJRJeX+qm
t4ZQu4JKTfxPNXKySCpTxOdtOa/B09tPBQnjUm+lDN3NPgitW86JD+RyireIUpLS
LHjy588EPpUIZov9vZacV3Ri17VIjAr5JSZWqWlj1xn24z0Mgxb0LIKvZW8/2/Ao
CpjoUimUUoaVxxbQZIKlIYt1ISD+kNbld6rSI09suQ2x9xE5sT0bMmaR6Z3V6PGo
GfeaJBErU82qP+lni1WHzElGGslpT07rQvqTM/GykNTO8QXe5bpWuIxTI6aLnJYH
BIVbCJz0vD4Ai1g9QzXt23ggEHx7mSTlVGMl5ydO83tk6MOy4PQnavu0bwfdphqY
ZNfzjZO5gEEt1LBihcV7
=Vu9c
-----END PGP SIGNATURE-----

--=_mehl.schokokeks.org-3896-1414402860-0001-2--

--===============0632682380851679968==
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

--===============0632682380851679968==--