Search the Community
Showing results for tags 'numlock'.
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 22.214.171.1248. 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
For some reason Affinity has stopped allowing me to enter the copyright symbol using Alt 0169 on the number pad. It was because Numlock was turned off.