Re: [Development] Question about keyboard mapping

[Randall OReilly]

Is this not incorporated into the main Qt codebase?  If not, why not?  I 
encountered a similar problem with the Mac Xserver in an earlier version of Qt 
(I think the first “fallback” fixed that but seems like this is a much more 
robust solution?).  Cheers,

- Randy

> On Oct 6, 2016, at 8:50 AM, Frank Richter  wrote:
> 
> Hi,
> I think what happened is that at some point keyboard handling on X11 was 
> changed to use xkb exclusively.
> This works fine if the server provides the xkb layout identity; this usually 
> is the case for non-ancient(?) X.org servers, but not necessarily for other 
> server vendors.
> Now, if that identity can not be determined, a fallback is used; still an xkb 
> keyboard layout from the local machine.
> Unfortunately, the "other" servers mentioned above may not use key codes that 
> match those from the local fallback layout, and you end up with weird 
> behaviour.
> (In my case it happened with Exceed, and keys were sort of "one off": you 
> pressed a key, but what appeared on screen was an adjacent letter...)
> 
> Anyway, the "solution" was to evaluate the keyboard mapping available through 
> the core protocol, and synthesize an xkb layout from that. This allows 
> keyboard input to work even if the server doesn't support xkb. You can find 
> patches here: https://github.com/res2k/QtLegacyXKeyboard
> 
> Hope I could help,
> -f.r.
> 
> On Mon, 3 Oct 2016 at 21:16 Scott Aron Bloom  wrote:
> I have had a bunch of customers report that using our tool over Xceed, 
> ASTEX-X, and now XManager, are having problems with the keyboard mapping.
> 
> Was there something fixed post Qt 5.5.1 for this type of issue?  I am stuck 
> on 5.5.1 for the near future, and will have to back patch it.
> 
>  
> 
> Scott
> 
> 
>  
> 
>  
> 
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Question about keyboard mapping

[Frank Richter]

Hi,
I think what happened is that at some point keyboard handling on X11 was
changed to use xkb exclusively.
This works fine if the server provides the xkb layout identity; this
usually is the case for non-ancient(?) X.org servers, but not necessarily
for other server vendors.
Now, if that identity can not be determined, a fallback is used; still an
xkb keyboard layout from the local machine.
Unfortunately, the "other" servers mentioned above may not use key codes
that match those from the local fallback layout, and you end up with weird
behaviour.
(In my case it happened with Exceed, and keys were sort of "one off": you
pressed a key, but what appeared on screen was an adjacent letter...)

Anyway, the "solution" was to evaluate the keyboard mapping available
through the core protocol, and synthesize an xkb layout from that. This
allows keyboard input to work even if the server doesn't support xkb. You
can find patches here: https://github.com/res2k/QtLegacyXKeyboard

Hope I could help,
-f.r.

On Mon, 3 Oct 2016 at 21:16 Scott Aron Bloom  wrote:

> I have had a bunch of customers report that using our tool over Xceed,
> ASTEX-X, and now XManager, are having problems with the keyboard mapping.
>
> Was there something fixed post Qt 5.5.1 for this type of issue?  I am
> stuck on 5.5.1 for the near future, and will have to back patch it.
>
>
>
> Scott
>
>
>
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Question about keyboard mapping

[Scott Aron Bloom]

I have had a bunch of customers report that using our tool over Xceed, ASTEX-X, 
and now XManager, are having problems with the keyboard mapping.

Was there something fixed post Qt 5.5.1 for this type of issue?  I am stuck on 
5.5.1 for the near future, and will have to back patch it.

Scott



___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development