microsoft/PowerToys

Better labeling for Keyboard Manager Remap of NumPad non 0-9 keys

Open

#21,375 opened on Oct 20, 2022

View on GitHub
 (4 comments) (0 reactions) (0 assignees)C# (7,978 forks)batch import
Help WantedIdea-EnhancementProduct-Keyboard Shortcut Manager

Repository metrics

Stars
 (133,154 stars)
PR merge metrics
 (Avg merge 14d 20h) (117 merged PRs in 30d)

Description

Description of the new feature / enhancement

The Keyboard Manager "Remap keys" function has remaps available for all the NumPad numbers (0-9), but there is one more NumPad key that is usually toggled with a NumLock key: the NumPad '.' (decimal point) button.

Usually a NumLock toggle that turns OFF NumLock will allow that key to function as "Delete". Unfortunately this one NumPad key has no listing in the "Remap keys" feature. If you could add that remap, it would make the NumPad remap options complete.

Scenario when this would be used?

I have a keyboard where the manufacturer has decided to make the NumPad keys numeric-only. (No NumLock toggle key)

For 30 years I've been using keyboards with a NumLock key that can toggle NumLock OFF. That way I can use the standard NumPad placement for directional keys, etc. (Home, End, PgUp, PgDn, etc. which are in standard placements on NumPads, but are in various non-standard placements elsewhere. Therefore my muscle memory is highly linked to the NumPad with NumLock toggled OFF. With a standard NumLock toggled OFF, the decimal place '.' button on the NumPad acts as a Delete button.) "Remap keys" is perfect for this remap purpose except for that one missing NumPad key remap option.

Supporting information

No response

Contributor guide

Research direction
Add the missing NumPad decimal point key (.) to the list of remappable keys in Keyboard Manager. Locate the existing NumPad key definitions and extend the enum/mapping to include VK DECIMAL (0x6E) or the corresponding virtual key code.
Tech stack
csharp
Domain
desktop
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70