Maniphest T74672

Blender doesn't implement ABNT2 keyboard layout correctly
Closed, Duplicate

Assigned To
None
Authored By
Crowe (crowe)
Mar 12 2020, 12:45 AM
Tags
  • BF Blender
  • User Interface
Subscribers
Anselm Schüler (schuelermine)
Crowe (crowe)
Germano Cavalcante (mano-wii)

Description

System Information
Operating system: Windows 8.1
Graphics card: GeForce GTX 1060

Blender Version
Broken: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: 77d23b0bd76f, type: Release
Worked: Never (earliest test done on 2.7)

Short description of error

The following keys don't work correctly in Blender when using a ABNT2 keyboard:

\ | ´ ` ç ~ ^ ] } ; : / ?

Numpad . Numpad ,

They either get confused with different keys or output nothing. This bug might actually be two closely related issues: defective UI inputs keyboard layout and wrong keymap keyboard layout.

I included a ANSI vs ABNT2 keyboard comparison below and the results when pressing these keys on UI field inputs like Material names and the Text editor, followed by what the Keymap sees when I try to assign them as shortcuts.

I see two issues here:

A. The UI uses a mostly correct keyboard layout, but it doesn't know the / ? and numpad . keys exist, and can't write ^ or ` unless you follow it with another ^ / `.

B. The keymap is likely using something similar to a ANSI layout instead of the OS layout. Just look at the keys placements; most problematic keys output what a ANSI keyboard would if I were using one. / ? and numpad . still missing.

Exact steps for others to reproduce the error

  1. Get a ABNT2 keyboard and configure your OS to use it.
  2. In Blender, type `´ [ { ç ~ ^ ] } ; : / ? \ | Numpad . Numpad , in the Text Editor and any input, like a Material name field.
  3. Open the Preferences panel and try to configure a shortcut with the keys above.

Related Objects

Mentioned Here
T66607: AccentGrave / Tilde not accessible on certain keyboards in Windows [makes Walk/Fly difficult to access]
rB77d23b0bd76f: Fix T73442 Overlay: Wireframe infront buggy in material shading mode

Event Timeline

Crowe (crowe) created this task.Mar 12 2020, 12:45 AM
Crowe (crowe) renamed this task from Blender doesn't implent ABNT2 keyboard layout correctly to Blender doesn't implement ABNT2 keyboard layout correctly.Mar 12 2020, 12:53 AM
Anselm Schüler (schuelermine) added a subscriber: Anselm Schüler (schuelermine).Mar 12 2020, 12:57 AM
Philipp Oeser (lichtwerk) added a project: User Interface.Mar 12 2020, 11:13 AM
Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Needs Information from User.Mar 12 2020, 3:00 PM
Germano Cavalcante (mano-wii) added a subscriber: Germano Cavalcante (mano-wii).

The character displayed for keymaps is different from the character that is typed (for example in the text editor).
The keymap tries to display the button and not character.
For example, for the keymap there is no difference between lowercase c and uppercase C, the important thing is to indicate which is the keyboard button.
So this is a known limitation and not a bug.

Please edit the report to describe only the non-keymap issue.

Crowe (crowe) added a comment.Mar 12 2020, 4:22 PM

@Germano Cavalcante (mano-wii) Okay. So two issues as suspected.

In the meanwhile someone pointed me in the direction of a bug report that must be the same keymap issue (T66607) so I'll mention it in a footnote in the report because not knowing about its existence can create confusion when testing any possible character layout patch, and I'll add the keyboard comparison to a comment in that other report. Sounds good?

Germano Cavalcante (mano-wii) added a comment.Mar 12 2020, 5:14 PM

You can add pertinent information in the comments of the other report.
Since it is the same problem, I will close this as a duplicate.