Skip to content

New Editor cannot map keys that don't physically exist #50360

Description

@dullahan8

Description of the new feature / enhancement

The classic version had a dropdown box that you could select any key that exists in the registry. The new version requires you to tap a key on your physical keyboard to map it.

Could the new version also have a dropdown box option available if the key is not available physically for the user to press?

Scenario when this would be used?

I required scroll lock and pause/break briefly today which is missing from my 70% keyboard. I decided that the Keyboard Manager would be able to easily solve my issue but I had to switch to the Classic editor to map those keys. I could not figure out a way to map those keys via the new editor.

Supporting information

Image Image

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Needs-TriageFor issues raised to be triaged and prioritized by internal Microsoft teamsProduct-Keyboard Manager

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions