Re: Different keycodes for shifted characters under Wayland vs X11

Thanks Vadim!

> 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.

I started from git checkout v3.2.2.1
I cherry-picked just this commit from @unxed :
https://github.com/wxWidgets/wxWidgets/commit/2c0f6a2aa0c8d0650d1f856aa279ce7495925c17

It didn't apply quite cleanly. I'm not sure if my merge was quite right but 
on re-build the keyboard sample had the correct behavior, and shift-3 
returns keydown '3'/51.

[image: wayland2.png]
Hope this is helpful!
-ck



On Saturday, April 29, 2023 at 6:36:46 AM UTC-7 Vadim Zeitlin wrote:

> 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/
>

-- 
Please read https://www.wxwidgets.org/support/mlhowto.htm before posting.
--- 
You received this message because you are subscribed to the Google Groups "wx-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/wx-users/7714a3e7-60d5-4ee0-a3d2-33bf66ec1199n%40googlegroups.com.