UI elements ignore keyboard layout changes (ex. Swapped CTRL / CAPS) #56312

New Issue

Jaggz H · 2018-08-11T12:57:05+02:00

Jaggz H commented

2018-08-11 12:57:05 +02:00

Linux, Debian (Stretch)
Windows 10

Windows: Official 2.79 download (no access to that system right now)
Linux: 2.79.6 git build, c19ddcc975
Worked: No clue

I swapped my CTRL and CAPSLOCK keys. Most everything seems to work fine, but the change is ignored in a few places. Example: CTRL C/V and CTRL Numpad +/- use the original physical CTRL key location.

Note: In Linux, xev shows the keycodes stay constant, while the keysyms change:

keycodes:

66 constant for Caps key's POSITION
37 constant for CTRL key's POSITION

keysyms:

0xffe5 for Caps, wherever you map it.
0xffe3 for CTRL, wherever you map it.

Steps to reproduce:

Swap your caps/ctrl keys.
Try copying/pasting a numerical or string field with CTRL C / V

General info on swapping Caps/Ctrl keys:

- In KDE this is found in:

System Settings -> Hardware -> Input Devices -> Advanced -> Ctrl key position -> Swap Ctrl and Caps Lock

- In Windows you can use their old set of tools (that still work):
-- Windows Server 2003 Resource Kit Tools
#-- Run as administator:

 C:\Program Files (x86)\Windows Resource Kits\Tools\remapkey.exe

#-- Credit to this page for more that info:

https://www.techrepublic.com/article/how-to-remap-the-caps-lock-key-and-avoid-future-frustration/

Linux, Debian (Stretch) Windows 10 Windows: Official 2.79 download (no access to that system right now) Linux: 2.79.6 git build, c19ddcc975f Worked: No clue I swapped my CTRL and CAPSLOCK keys. Most everything seems to work fine, but the change is ignored in a few places. Example: CTRL C/V and CTRL Numpad +/- use the original physical CTRL key location. ## Note: In Linux, xev shows the keycodes stay constant, while the keysyms change: ### keycodes: 66 constant for Caps key's POSITION 37 constant for CTRL key's POSITION ### keysyms: 0xffe5 for Caps, wherever you map it. 0xffe3 for CTRL, wherever you map it. # Steps to reproduce: - Swap your caps/ctrl keys. - Try copying/pasting a numerical or string field with CTRL C / V ## General info on swapping Caps/Ctrl keys: # - In KDE this is found in: System Settings -> Hardware -> Input Devices -> Advanced -> Ctrl key position -> Swap Ctrl and Caps Lock - - In Windows you can use their old set of tools (that still work): - -- [Windows Server 2003 Resource Kit Tools ](https://www.microsoft.com/en-us/download/details.aspx?id=17657) #-- Run as administator: ``` C:\Program Files (x86)\Windows Resource Kits\Tools\remapkey.exe ``` #-- Credit to this page for more that info: ``` https://www.techrepublic.com/article/how-to-remap-the-caps-lock-key-and-avoid-future-frustration/

Jaggz H commented

2018-08-11 12:57:05 +02:00

Added subscriber: @jaggz

Bastien Montagne commented

2018-08-11 15:24:32 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2018-08-11 15:24:32 +02:00

Mmmhhh… I thought we only were using keysyms in GHOST… but maybe things like modifier keys also use keycode info… :/

Jaggz H commented

2018-08-12 07:49:08 +02:00

Are these assignable in the Prefs -> Input? I can't find them.

(I was attempting to assign Ctrl MouseWheel to the function to scale individual Window UI elements, in addition to CTRL Num+/-).

Are these assignable in the Prefs -> Input? I can't find them. (I was attempting to assign Ctrl MouseWheel to the function to scale individual Window UI elements, in addition to CTRL Num+/-).

Sybren A. Stüvel commented

2020-02-11 11:55:05 +01:00

Added subscriber: @dr.sybren

Sybren A. Stüvel commented

2020-02-11 11:55:05 +01:00

Changed status from 'Confirmed' to: 'Needs User Info'

Sybren A. Stüvel commented

2020-02-11 11:55:05 +01:00

@jaggz It's good to see a fellow user of {key Caps-as-Ctrl} :-)

I can't reproduce this issue, though. For me {key Caps-as-Ctrl C} and {key Caps-as-Ctrl V} over a numerical or string field works just fine. I'm testing with master @ be8879718e. xev also gives me the same key codes and symbols as in your report, showing that we're using the same way to remap the keys.

@jaggz It's good to see a fellow user of {key Caps-as-Ctrl} :-) I can't reproduce this issue, though. For me {key Caps-as-Ctrl C} and {key Caps-as-Ctrl V} over a numerical or string field works just fine. I'm testing with master @ be8879718e24e417d299eb298b8a9d4d2ca324ee. `xev` also gives me the same key codes and symbols as in your report, showing that we're using the same way to remap the keys.

Jaggz H commented

2020-02-16 17:00:01 +01:00

Changed status from 'Needs User Info' to: 'Resolved'

Jaggz H closed this issue

2020-02-16 17:00:01 +01:00

Jaggz H self-assigned this 2020-02-16 17:00:01 +01:00

Jaggz H commented

2020-02-16 17:00:01 +01:00

Ctrl <-> Caps flipping was really worth it.
Seems fine in 2.8+. Resolving.

Ctrl <-> Caps flipping was really worth it. Seems fine in 2.8+. Resolving.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

UI elements ignore keyboard layout changes (ex. Swapped CTRL / CAPS) #56312

Note: In Linux, xev shows the keycodes stay constant, while the keysyms change:

keycodes:

keysyms:

Steps to reproduce:

General info on swapping Caps/Ctrl keys:

- In KDE this is found in: