musescore / musescore/MuseScore

Unable to remap numeric keypad (NumPad) keys

Open
#17,080 8 comments 2 reactions 1 assignee View on GitHub

@Eism is already working on this.

Since Mar 30, 2023.

P2 regression MS3 UI
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UI bug

Bug description

When I try to remap the numeric keypad keys, MuseScore actually just remaps the regular number keys. For example (since I find the default mapping counterintuitive) I want e.g. '4' on the keypad to be a quarter note. When I remap it, hitting '4' on the keypad doesn't return 'Num4' as it should, but instead '4'. No combination of modifiers gets MuseScore's remapper to recognize Num4...

I've confirmed that other applications that differentiate between keypad and number-row do recognize the difference, such as Pro Tools. Also, Karabiner EventViewer also returns different codes for keypad vs number-row. So I don't think my system has a problem.

This is MuseScore 4.0.2 on two Macs ~ M1 Macbook Air with Ventura 13.3, and i9 iMac with Monterey 12.6.3.

Steps to reproduce
  1. Open Preferences->Shortcuts
  2. Find a shortcut to modify, and double click it to open the "Define shortcut" popup
  3. Press a numeric keypad key
  4. You'll see that instead of e.g. "Num4", the value "4" is defined, which corresponds only to the number 4 on the number-row.
  5. Close the dialog, and try to use the new shortcut via the number pad
  6. Nothing happens.
Screenshots/Screen recordings

video on youtube (too big to add here)
https://youtu.be/lLz0cgRSruI

MuseScore Version

4.0.2

Regression

Yes, this used to work in Musescore 3.x and now is broken

Operating system

MacOS 13 and MacOS 12

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.