https://bugs.kde.org/show_bug.cgi?id=413310
--- Comment #4 from Oded Arbel <o...@geek.co.il> --- The new subject seems counter-intuitive: the original issue is that kwin does indeed differentiate between numpad keys and standard number keys - if you try to use the numpad numbers to access menu accelerators you'd find they do nothing. 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 this all boils down (again, like a few other reported bugs, e.g. bug 453661, bug 444537 and bug 470256) to the fact that global shortcuts should use the concept of physical keys (i.e. what is the position of the key that was pressed on the keyboard) while things that look like typing text (e.g. menu accelerators) should use logical keys (i.e. what character a key generates based on the software configuration) - though it looks like currently it is the reverse. As in the bugs mentioned above, I blame Qt. As to bug 446389 - I do not think it is an actual duplicate. It may be closely related, though I'm not familiar with what implements these two - quite distinct behaviors - so I'll defer to Nate's opinion. -- You are receiving this mail because: You are watching all bug changes.
