https://bugs.kde.org/show_bug.cgi?id=413310
--- Comment #6 from tomash...@gmail.com --- (In reply to Oded Arbel from comment #4) > But the other issue is also correct - the shortcut editor does accept numpad > numbers in shortcuts and treats them to be identical to standard number > keys, and when used - they work: i.e. numpad keys trigger shortcuts set with > standard number keys and vice versa. Assuming that both are handled in kwin, > this is confusing to me, and also I'm not sure what is the correct behavior > - numpad keys are a useful shortcut to find the correct number key without > looking (they are better arranged for that) so I would like to use them for > pre-set actions that cannot be customized - like menu accelerators, but I > also understand why people would want to use them for different global > shortcuts than standard number keys. > I think a good design would be this: 1) If for a given number there is no separate action set for keypad key and for above-the-keyboard key, treat them as the same. 2) It there are separate actions, treat them separately. 3) When assigning shortcuts, treat above-the-keyboard keys as plain numbers and when using keypad number, ask the user if they want to use specifically keypad key that would apply to this key only or generic number that would apply both to it and the above-the-keyboard key. In practice, let's say CTRL+1 is set to "close a window" and nothing else is set. Both CTRL+1 and CTRL+KP1 close a window. Now I try to assign CTRL+KP1 to "close tab". So I am asked if I want to assign a separate action just for the keypad key or if I want to change the meaning of CTRL+1 from closing window to closing a tab. However, that would be a nice bonus, for start, making sure the shortcuts work for both above-the-keyboard and keypad keys would be great:-). -- You are receiving this mail because: You are watching all bug changes.
