Search the Community
Showing results for tags 'numeric'.
-
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
-
I would like to request that the numeric keys, which are used to set the opacity of an object by default, become available for editing within the keyboard shortcuts section of the preferences. The reason for this is that these keys are very accessible, which is the reason I would like to use them to toggle between Photo's personas and edit inside of Photo/ Designer. Unfortunately though, some shortcuts will override the opacity shortcuts and others won't. This causes inconsistencies as discussed here:
-
- keyboard shortcuts
- shortcuts
- (and 8 more)
-
I know, I can move by typing x or y plus …, but if possible, it would be great I can do this in the Transformation Menu like this ...
-
By default the number keys set opacity - which is fine. BUT AD doesn't distinguish between the standard numbers and the numeric keypad, to which I'd really like to assign a bunch of other shortcuts. With 15 keys on the numpad, and at least 3 different modifiers, there are >45 keyboard shortcuts going to waste here! Also, under the current system, if I do set a numeric keypad numeral as a shortcut, it doesn't warn me that there is an existing clash with the opacity function... worst of both worlds! Thanks for your consideration.
-
Dear (epic) people at Affinity, I have a feature request regarding consistency, example: when using the "transform" tab, you can easily adjust sizes by hovering over the options and scrolling up/down — could you implement this in the text tool as well? Possibly in every dropdown option that entails numeric options. Thank you. Kind regards, Jo
-
- scroll
- adjustment
-
(and 4 more)
Tagged with: