Search Issue Tracker
By Design
Votes
2
Found in
2017.1.0b10
Issue ID
924468
Regression
No
Number shortcut for MenuItem doesn't work with numeric keypad
Steps to reproduce:
1. Open attached project "924468.zip"
2. Open Scene View
3. Press '1(alphanumeric keyboard)' and '1(alphanumeric keyboard) + shift'
*everything works as intended*
4. Turn on Num Lock
5. Press '1(numeric keypad)' and '1(numeric keypad) + shift'
Expected behavior: number shortcut for MenuItem works from alphanumeric keyboard and numeric keypad
Actual behavior: number shortcut for MenuItem doesn't work with numeric keypad
Reproducible with: 5.5.4p1, 5.6.2f1, 2017.1.0f1, 2017.2.0b1
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
The goal is eventually make the keypad numbers bindable as well, so we want those 2 set of keys to be independent.