https://bugs.documentfoundation.org/show_bug.cgi?id=156443
--- Comment #10 from Mike Kaganski <mikekagan...@hotmail.com> --- (In reply to V Stuart Foote from comment #9) > But don't the VK_NUMPAD[0-9] emit different scancodes to the VK_[0-9]? Hex > values (and decimal) of 0x60 -- 0x69 (96-105), 0x30 -- 0x39 (48-57) > respectively. [1][2] Indeed. We are able to disambiguate ~all keys on keyboard. If wanted, we can also keep the numpad numbers for Alt-extended characters, and other numbers for shortcuts. This still requires fixing bug 158112 (e.g., exactly this way: making Alt+Number shortcuts only work for non-numpad numbers) first, as I explained in comment 3. > The 'EnableHexNumpad' flavor ALT codes maybe needing a bit more handling, > but by that point our <Alt>+x toggle already services Unicode centric users. EnableHexNumpad may be a separate issue, if needed. I mentioned it here, but with a note that "a follow-up enhancement could be filed for that". So it may be excluded from consideration here. However, I would think that Alt+NonNumpadNumber shortcut would still be confusing. Also, listing the Alt+Number in customization provokes for using it; and people who will try will *mostly* complain that it doesn't work: they would expect numpad numbers to do what they expect from the shortcut, and see it doesn't (because it would be used for Alt+Numpad Number extended character function). I am strongly in favor of removing Alt+Number as an assignable key combination on Windows, completely. -- You are receiving this mail because: You are the assignee for the bug.