Re: Discrepancy between XCB and X11 MappingNotify

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

From: [email protected]
Date: Thu, 03 Apr 2025 21:40:33 +0000

> I'm confused. Let's say there is an X11 application out there which was m=
ade for
> a libX11 version not using XKB (expecting to get MappingNotify events). N=
ow when
> this application is linked with another libX11 library built with XKB, th=
en
> this application will no longer work. I want to know whose decision it wa=
s to
> forcefully include XKB like that, it just seems odd to me. But it looks l=
ike
> this dates back to earlier than 2003 so it's only a deal in my hypothetic=
al
> scenario.

Yeah, checked X11R5 which doesn't have this "feature", so it happened
sometime between 1991 and 2003. I'd suggest fixing it, but that seems
more likely to break things than help...

> There was one more thing in the Stackoverflow post which was what I menti=
oned
> where XKeysymToKeycode(dpy, XK_F1) is used to "cache the modifier and key=
map
> information" which (I tried it, it actually worked) yields MappingNotify =
events.
> This really does not make sense in my head.

Nor mine. I'd have to dig through the code a bunch to figure out why
that helps...

=2D-=20
=2Dkeith

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEw4O3eCVWE9/bQJ2R2yIaaQAAABEFAmfvMPYACgkQ2yIaaQAA
ABGZGw//agcRVJgbYkTqesl6jdg4HKqIJ1xecm6A90W1Ww2fF6jXAuppFUAnRwic
qDLhm3gR74UjGU7yCqIU68wlkdxv13z4M2N0UClZzTShsqAeyjWffr9L8/nB+KPj
/HcZNU5MzlVNBcVDDAdqb74UY8CVFi+S8UV0AoVNIEtbS3reMJy18RgdyPST0Jys
znTYTS3xRypYjWdoDHBUv0w2YdZM1Lr9kC6OPDuIhCy6c9z/KV81DKDNTUN7z34o
RSCZB+cU1XkO8sz02EN/7Ekf0WklG0itj63tisQom3NEa/2g64DKifqgAddVlziT
AfzYo75/FYrqiKgonkRp6kN01ebaA/bjSXmLJxEP+y5Pf0pGKK9fxPQ5y7is3yOm
TBf8Lb4VHMlh7vNpZOFMIXsUv7Lq+OD20sxG0Ri567c/NSi1BlsifnL+bQ0CzG/+
5t4oNwXzYjmq/p4Q/xWVd5o6yssqAlp3LYmYKVcj61iwWmL3z7/FIi0AlHiH+wxm
BDcCxgGjfLpXy7rtmg728RxSHfPARkT+9SOp02Paz5Zkj1WF5lCoUnY5d64NiKlv
BxJC2TzKDFusqnNoEUdzuHCQO5nxlejVFSf6CXw5kprHYCL77pvJlaTLUBOoFwbu
+RjNcIi6OUBFvj8hscYZqChiVwJXbTgiRUJBjlnnFBaH/s4BKC4=
=yVOO
-----END PGP SIGNATURE-----
--=-=-=--