Search the Community
Showing results for tags 'numpad'.
-
Hey all, Is there any way to recognise/use the enter key on the numeric keypad as a »regular« enter key? I can't get it mapped as I don't even know where I would set it under the shortcuts. But I would find it incredibly more intuitive this way than having to reach across half the keyboard afterwards to confirm (or alternatively use the mouse to find the appropriate button to confirm) after entering values in a transform process. I noticed this especially during the cropping process with the cropping tool in Photo. I would like to confirm the process, but the numeric keypad enter key is not assigned at all and only gets the error tone. Can someone point me in the right direction on how to set this up, if that's even possible? And if not: well, why hasn't that been an option for a long time? I couldn't be the only one who was bothered by this, could I? 😅 Cheers!
- 4 replies
-
- affinity suite
- numpad
- (and 8 more)
-
Problem Keyboard shortcuts on the numpad are rather limited in functionality (apart from the fact that there is no differentiation between the numeric row and numpad keys), because the Shift key negates Numlock. This means that Shift+Numpad key activates the secondary function (as if numlock was turned off). It invokes Home, End, PgUp, PgDown, Left, Right, Up, Down and Clear. This means that any combination of keyboard shortcuts with the shift key becomes 'invalid' since it replicates a key that is accessed with a single press. Considering that any keyboard with a numpad has access to these stand-alone keys, it makes little sense that they are registered this way. I know some applications are faced with the same limitation, however, some (such as Blender) don't have this issue. This is on Windows 10, UK keyboard, US International layout, using 1.10.4.1198. Observation Apart from creating redundant key sequences, some of the combinations cannot seem to be assigned properly, for instance if I assign shift + Numpad 5 as keyboard shortcut, it registers as "clear". Shift + Alt + Numpad 5 becomes Alt + Clear, and Ctrl + Shift + Alt + Numpad 5 is impossible to enter, because the value box remains active on "Ctrl + Alt + Clear". Notice that the any commands assigned to key-sequence with "Clear" as value work as intended. However, it does not register when using the regular 5 key, so it is actually recording a different input than a numeric key. Expectation I expect the key-sequence to show the numbers the same way as the numeric row does, so they won't circumvent numlock when using the numpad. Better solution Or better yet, any numpad key should be registered as Num(pad) [key]. This is how Blender does it and that way, any key from the numpad, whether 1-9 or / * - + . key, they will register without issues and most importantly, may be used for additional shortcuts, see and