Re: Different keycodes for shifted characters under Wayland vs X11

On Sat, 29 Apr 2023 02:49:18 -0700 (PDT) [email protected] wrote:

c> Linux (Ubuntu 22.04 LTS)
c> 
c> Run the 'keyboard' sample and press <shift>-3 to type a ‘#’ character.
c> 
c> Under X11 (forced by setting GDK_BACKEND=x11 env var), I get the same 
c> behavior I see on MacOS and Windows: keydown on ‘3 (code=51)’, with shift 
c> modifier set.

 This is the correct/expected behaviour.

c> $ GDK_BACKEND=x11 ./wxWidgets-3.2.2.1/buildgtk/samples/keyboard/keyboard 
c> 
c> Under Wayland (no env var set, default for Ubuntu 22.04), I see keydown on 
c> ‘#’ (code=35), with shift modifier set.

 This is a bug. The good news is that it has already been fixed in master,
i.e. running the same sample in it yields the expected results with
Wayland. The bad news is that I'm not sure which fix exactly has fixed it.
It must be one of the changes done by @unxed (who has been doing great work
on ensuring that key events generation works consistently and correctly in
all ports), but I'm not sure which one exactly. If you have time to look at
it, please try to check which of the master commits should be backported to
3.2 to fix this.

 Thanks,
VZ

-- 
TT-Solutions: wxWidgets consultancy and technical support
               http://www.tt-solutions.com/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)

iEYEABECAAYFAmRNHWoACgkQBupB3k9sHoYQ2QCeL4DTtxD96qCVLTPtXm+2QDBz
10QAoJVHUpBdb16K5iklS5dZfNE738LN
=9FFY
-----END PGP SIGNATURE-----