Bug 157645 - Missing keyboard keys for shortcuts
Summary: Missing keyboard keys for shortcuts
Status: RESOLVED DUPLICATE of bug 115052
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-06 23:02 UTC by skagon
Modified: 2023-10-07 15:44 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description skagon 2023-10-06 23:02:27 UTC
Description:
In the Tools–Customise–Keyboard dialog, the available keyboard keys are missing some keys which are readily available in the USB HID keycode spec. Specifically:
F17-F24 (strangely, F13-F16 do exist)
All keypad keys
\| (backslash key)
`~ (tilde)
Non-US #
Plus a number of other keys, such as International 1-9, all of which are specified in [https://www.usb.org/sites/default/files/hut1_4.pdf], in the Keyboard page.

I would suggest that the missing keys be added in the list. Moreover, an overhaul of the shortcut selection page is advised, so that keys and modifier combinations are easier to handle, rather than one very long list of "all" possible combinations.


Steps to Reproduce:
1.Open Tools – Customise…
2.Go to Keyboard tab
3.Enjoy

Actual Results:
Keys missing from shortcut key list.

Expected Results:
All keyboard keys present, perhaps even a "press combination" field to detect any key combination.


Reproducible: Always


User Profile Reset: No

Additional Info:
https://www.usb.org/sites/default/files/hut1_4.pdf pages 89-95
Comment 1 V Stuart Foote 2023-10-07 15:44:11 UTC
the defined keysyms available to LibreOffice UI currently are:

https://opengrok.libreoffice.org/xref/core/include/vcl/keycodes.hxx

with API defs:

https://api.libreoffice.org/docs/idl/ref/namespacecom_1_1sun_1_1star_1_1awt_1_1Key.html

discussion on dupe and friends.

*** This bug has been marked as a duplicate of bug 115052 ***