Shortcut display wrong symbol or are not detected in keymap with French Azerty keyboards #104787

New Issue

Samuel Bernou · 2023-02-15T18:36:57+01:00

Samuel Bernou commented

2023-02-15 18:36:57 +01:00

System Information
Operating system: Linux-5.4.0-58-generic-x86_64-with-glibc2.31 64 Bits
Graphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.29.05

Blender Version
Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: rB55485cb379f7
Worked: (newest version of Blender that worked as expected)

Short description of error

Using French Azerty keyboard, setting keymap item shortcuts displays wrong symbols with some keys, sometimes with bad behaviors.

Some write the character that is supposed to be entered while pressing Shift (upper label of the key when it should be lower label).
Sometimes it just displays something plain wrong.

Having the wrong label is problematic when you search by key-binding to disable duplicates. Because you need to type the right symbol, that isn't related to the real key.

Detected Key labels are different on Linux and Windows

Here tested on a Windows 10:

Linux Mint (machine used for the bug report):
Note: On linux mint, some keys can't be assigned at all (show warning: Unsupported key: Unknown)

Exact steps for others to reproduce the error

Use an azerty keyboard with keyboard language set to French.
Try to enter key shortcut in keymap with special character (there are more than showed in screenshots)

**System Information** Operating system: Linux-5.4.0-58-generic-x86_64-with-glibc2.31 64 Bits Graphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.29.05 **Blender Version** Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: `rB55485cb379f7` Worked: (newest version of Blender that worked as expected) **Short description of error** Using French Azerty keyboard, setting keymap item shortcuts displays wrong symbols with some keys, sometimes with bad behaviors. Some write the character that is supposed to be entered while pressing Shift (upper label of the key when it should be lower label). Sometimes it just displays something plain wrong. Having the wrong label is problematic when you search by key-binding to disable duplicates. Because you need to type the right symbol, that isn't related to the real key. Detected Key labels are different on Linux and Windows Here tested on a Windows 10: ![azerty_fr-wrong_keys_windows_part1.png](/attachments/628e9c09-b80a-4eb4-a9ff-355a26b164ea) ![azerty_fr-wrong_keys_windows_part2.png](/attachments/6109564d-40d2-4dee-9546-d7f47b53c191) Linux Mint (machine used for the bug report): Note: On linux mint, some keys can't be assigned at all (show warning: `Unsupported key: Unknown`) ![azerty_fr-wrong_keys_linux_mint_part1.png](/attachments/9d0d3e19-9cfd-49dd-851a-e6d3791c119e) ![azerty_fr-wrong_keys_linux_mint_part2.png](/attachments/48c654a2-8176-4353-a94c-cf2de8165a8f) **Exact steps for others to reproduce the error** Use an azerty keyboard with keyboard language set to French. Try to enter key shortcut in keymap with special character (there are more than showed in screenshots)

azerty_fr-wrong_keys_windows_part1.png

88 KiB

azerty_fr-wrong_keys_linux_mint_part1.png

112 KiB

azerty_fr-wrong_keys_linux_mint_part2.png

96 KiB

azerty_fr-wrong_keys_windows_part2.png

65 KiB

Samuel Bernou added the

labels 2023-02-15 18:36:58 +01:00

Richard Antalik commented

2023-02-16 04:59:41 +01:00

From what I know, Blender assumes US keyboard layout for shortcuts. This is because you can work with different layouts and shortcuts will be in same physical position.

Issue with for example shortcht that calls pie menu is caused by 2 keyboard shortcuts assigned to same key. You need to disable or remove one you don't want to work. Please check if this resolves your issue.

From what I know, Blender assumes US keyboard layout for shortcuts. This is because you can work with different layouts and shortcuts will be in same physical position. Issue with for example shortcht that calls pie menu is caused by 2 keyboard shortcuts assigned to same key. You need to disable or remove one you don't want to work. Please check if this resolves your issue.

Richard Antalik added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-02-16 05:02:58 +01:00

Samuel Bernou commented

2023-02-16 17:57:20 +01:00

Yes indeed, the dot key was just a conflicting keymap item.
Did not see that and thought the last created item would take precedence (wrongly).
So in the end they just have both the wrong label, also why it's easy to miss the duplication when you refer to key label.

As you just confirmed, I supposed everything was based on Qwerty US ANSI and just handling keycode the same way for every keyboard.

But I wondered if there would be a way to display the right label according to detected system keyboard language.

Still, the most problematic part is the keys that doesn't work at all on Linux.

Yes indeed, the dot key was just a conflicting keymap item. Did not see that and thought the last created item would take precedence (wrongly). So in the end they just have both the wrong label, also why it's easy to miss the duplication when you refer to key label. As you just confirmed, I supposed everything was based on Qwerty US ANSI and just handling keycode the same way for every keyboard. But I wondered if there would be a way to display the right label according to detected system keyboard language. Still, the most problematic part is the keys that doesn't work at all on Linux.

Richard Antalik commented

2023-02-17 02:59:19 +01:00

Still, the most problematic part is the keys that doesn't work at all on Linux.

Can you check if this keys work in text editor? This may be bit different issue and I would perhaps focus this report on that.

All other imperfections are valid points I would say, but these are rather requests for improvement, than actual bugs. For that I would recommend https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
This tracker is limited for bugs.

> Still, the most problematic part is the keys that doesn't work at all on Linux. Can you check if this keys work in text editor? This may be bit different issue and I would perhaps focus this report on that. All other imperfections are valid points I would say, but these are rather requests for improvement, than actual bugs. For that I would recommend https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests This tracker is limited for bugs.

Samuel Bernou commented

2023-02-20 18:36:01 +01:00

The keys work as expected in Blender text editor.

The ISO key (bottom-left next to shift) write a < character normally.

The "special accent" key (near Enter) works as expected as well, but I don't know if the problem come from it being a "dead key", you press it one time, not writing anything, then press the character that will be inserted with the accent.

The keys work as expected in Blender text editor. The ISO key (bottom-left next to shift) write a `<` character normally. The "special accent" key (near Enter) works as expected as well, but I don't know if the problem come from it being a "dead key", you press it one time, not writing anything, then press the character that will be inserted with the accent.

Richard Antalik commented

2023-03-02 15:31:35 +01:00

The keys work as expected in Blender text editor.

The ISO key (bottom-left next to shift) write a < character normally.

The "special accent" key (near Enter) works as expected as well, but I don't know if the problem come from it being a "dead key", you press it one time, not writing anything, then press the character that will be inserted with the accent.

It could be, that it is not really sending any data. Can you check if that is the case when you run Blender with --debug-events argument? The output will be quite noisy, so I would recommend having mouse outside of Blender ready to copy stuff from console that possibly appears when you press the key.

> The keys work as expected in Blender text editor. > > The ISO key (bottom-left next to shift) write a `<` character normally. > > The "special accent" key (near Enter) works as expected as well, but I don't know if the problem come from it being a "dead key", you press it one time, not writing anything, then press the character that will be inserted with the accent. > It could be, that it is not really sending any data. Can you check if that is the case when you run Blender with `--debug-events` argument? The output will be quite noisy, so I would recommend having mouse outside of Blender ready to copy stuff from console that possibly appears when you press the key.

Samuel Bernou commented

2023-04-06 12:10:55 +02:00

Hi, sorry for the delay.

Here is the debug-events console log, tested on 3.4.1 and 3.5

With < (ISO key, bottom-left next to shift).

wm_event_do_handlers: Handling event
wmEvent type:171/UNKNOWN, val:1/PRESS, prev_type:1/LEFTMOUSE, prev_val:2/RELEASE, modifier={}, keymodifier:0, flag:{}, mouse:(600,435), utf8:'<', pointer:0x7f2ff957afd8

wm_event_do_handlers: Handling event
wmEvent type:171/UNKNOWN, val:2/RELEASE, prev_type:171/UNKNOWN, prev_val:1/PRESS, modifier={}, keymodifier:0, flag:{}, mouse:(600,435), utf8:'', pointer:0x7f2fb4c82658

With ^ (Special Diacritic "dead-key", near Enter)

wm_event_do_handlers: Handling event
wmEvent type:171/UNKNOWN, val:1/PRESS, prev_type:235/LEFT_BRACKET, prev_val:2/RELEASE, modifier={}, keymodifier:0, flag:{}, mouse:(1051,365), utf8:'^', pointer:0x7f2ff957acb8

wm_event_do_handlers: Handling event
wmEvent type:235/LEFT_BRACKET, val:2/RELEASE, prev_type:171/UNKNOWN, prev_val:1/PRESS, modifier={}, keymodifier:0, flag:{}, mouse:(1051,365), utf8:'', pointer:0x7f2fb4c4c4b8

Hi, sorry for the delay. Here is the debug-events console log, tested on 3.4.1 and 3.5 With `<` (ISO key, bottom-left next to shift). ``` wm_event_do_handlers: Handling event wmEvent type:171/UNKNOWN, val:1/PRESS, prev_type:1/LEFTMOUSE, prev_val:2/RELEASE, modifier={}, keymodifier:0, flag:{}, mouse:(600,435), utf8:'<', pointer:0x7f2ff957afd8 wm_event_do_handlers: Handling event wmEvent type:171/UNKNOWN, val:2/RELEASE, prev_type:171/UNKNOWN, prev_val:1/PRESS, modifier={}, keymodifier:0, flag:{}, mouse:(600,435), utf8:'', pointer:0x7f2fb4c82658 ``` With `^` (Special Diacritic "dead-key", near Enter) ``` wm_event_do_handlers: Handling event wmEvent type:171/UNKNOWN, val:1/PRESS, prev_type:235/LEFT_BRACKET, prev_val:2/RELEASE, modifier={}, keymodifier:0, flag:{}, mouse:(1051,365), utf8:'^', pointer:0x7f2ff957acb8 wm_event_do_handlers: Handling event wmEvent type:235/LEFT_BRACKET, val:2/RELEASE, prev_type:171/UNKNOWN, prev_val:1/PRESS, modifier={}, keymodifier:0, flag:{}, mouse:(1051,365), utf8:'', pointer:0x7f2fb4c4c4b8 ```

Thomas Dinges added

Status

Needs Triage

and removed

Status

Needs Information from User

labels 2023-05-12 14:55:41 +02:00

Pratik Borhade commented

2023-07-31 08:38:57 +02:00

Hi, I can confirm that some key characters are detected incorrectly with AZERTY layout.

Blender assumes US keyboard layout for shortcuts

I'm not sure about this. ZQSD are detected correctly.

Hi, I can confirm that some key characters are detected incorrectly with AZERTY layout. > Blender assumes US keyboard layout for shortcuts I'm not sure about this. ZQSD are detected correctly.

Pratik Borhade added

and removed

labels 2023-07-31 08:39:14 +02:00

Yevgeny Makarov commented

2023-07-31 13:20:24 +02:00

I guess the main task is Support for binding additional keys #73196

How to handle non US keymaps?

@PratikPB2123 - If it is Latin alphabet then probably most of it will work, but for example in Russian (Cyrillic) layout not a single letter key is recognized.

There are dozens of reports on this subject for different OS and languages.
There is no support for non-English layout, no dead key handling, etc.

I guess the main task is **Support for binding additional keys** #73196 > How to handle non US keymaps? @PratikPB2123 - If it is Latin alphabet then probably most of it will work, but for example in Russian (Cyrillic) layout not a single letter key is recognized. There are dozens of reports on this subject for different OS and languages. There is no support for non-English layout, no dead key handling, etc.

👍 1

Pratik Borhade commented

2023-08-01 07:22:05 +02:00

Thanks @jenkm . Indeed same as #73196
Will mark this as duplicate.

Thanks @jenkm . Indeed same as #73196 Will mark this as duplicate.

Pratik Borhade closed this issue

2023-08-01 07:22:07 +02:00

Blender Bot added

Status

Archived

and removed

Status