Re: WM_NAME vs. _NET_WM_NAME
Florian Bruhin <[email protected]> Mon, 27 Oct 2014 09:22:15 +0100
| Newsgroups | gmane.comp.gnome.wm-spec |
|---|---|
| Message-ID | <20141027082215.GA4524@lupin> |
This is a MIME-formatted message. If you see this text it means that your E-mail software does not support MIME-formatted messages. --===============3276720450201428009== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=_mehl.schokokeks.org-9284-1414398136-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-9284-1414398136-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 08:59:17 +0100]: > > While developing a Qt application, I noticed some bugs regarding to > > window title handling [1][2][3]. >=20 > I assume that's Qt 5, right? Indeed, it works fine with Qt 4. > > It seems the Qt toolkit only sets _NET_WM_NAME and doesn't set WM_NAME > > at all. Now that raises some questions: > >=20 > > - Should a client also set WM_NAME when setting _NET_WM_NAME? Sure, > > 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=20 > indication that a client is supposed to set it. Given that it's certainly= not=20 > a bug on Qt's side. If a window manager has problems with it, it's more= =20 > because the window manager doesn't support EWMH. 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 ;) > Qt 5's XCB backend doesn't support many "deprecated" features where there= is a=20 > EWMH replacement. For example it also doesn't support setting a window ic= on=20 > through the WM_HINTS (ICCCM section 4.1.2.4) property. Given that I=20 > interpreted this as a design decision to not support the "deprecated" hin= ts in=20 > the new implementation. Do you mean the backend as in a part of Qt, or xcb itself? > At the same time knowing the Qt development I am sure they would accept= =20 > patches if it improves the interoperability. I unfortunately don't feel comfortable enough with C++ to work on Qt (I'm using PyQt). > > - Should a window manager which implements EWMH act correctly when a > > client sets _NET_WM_NAME but not WM_NAME? (see [2]) >=20 > I do not really understand this question. I looked at the bug report and = would=20 > say that's a hebstluftwm bug. For comparison KWin handles the situation w= ith=20 > Qt 5 windows correctly. Okay. The question basically "is it the WM's fault, or Qt's fault" ;) > Shameless plug: as you are using Qt 5, consider using KF5::WindowSystem w= hich=20 > is a nice Qt 5 (only, no further KDE dependencies) library implementing E= WMH,=20 > supporting fallback to ICCCM if needed. It's the library powering KWin an= d=20 > Plasma (e.g. taskmanager) and also used in LXQt. 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 Thanks, 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-9284-1414398136-0001-2 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJUTgC3AAoJEJFusMj9VaByhLoP/1Zu7MRpgdedkLrUKeR2E866 4PiA6TysMAvWxXYOJLX1vmgSxmiLIq62yuS8/mcsE/p/0ulNrDT7NRTs1DWjHDk/ bBiwBkgB0HZPzI/kKbZqyh0hrAbLYyuHj9i0eK21nsYpisxKHL0407+M7LtPXuG3 DcoMv3eIB2ANJbiJvEmBSa9d2ej53Hh40A8roYbjTiWvouUpexAbLv7BlIg1MWXD DQV2r6GtHANxRAznvnc0dYB+VuSVA8jBm6G+h6+TALjw8/VL0HvwTQnG3lq+ZOw1 KbaYC9TId9gnx0ifmPi36ZmNs+4GhKoZGXUno1sc5HCSIbLl4H2Xu4j8nfC6gt1L vWwX5xo7aqb9gsHzF7UK7yVD0FwRwoPP7X/9ewPyBk3ecfmQLBD24aBustZLSrcE MbJNg7mIr2YCXQM/T0wFPw3qO2Q79Tz265T4IfcvpHI87hiUi3nlf02fNZsUQFhQ mB5peASRh9VSb/XURRA53UxPD7CU6+IVEvdbqhHrYUykef3JqdFcoV5mzDq+LJf0 nLvo+NH29GGFVR4mx0d+YfKTWwsq4xvEwtBUMbGgKhE0g3duwNAnotd8DVuC5qik H9BsuI8mU1W5kJem4KMGzNl3MQxzsW23TqYGDkV73nlN83uG1LCeU7Ldux7u4UCB q80ArlsfrqQFaA97cZTj =1xIx -----END PGP SIGNATURE----- --=_mehl.schokokeks.org-9284-1414398136-0001-2-- --===============3276720450201428009== 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 --===============3276720450201428009==--