musescore / musescore/MuseScore

The percussion panel does not appear when piano keyboard is in view

Open
#28,409 3 comments 0 reactions 2 assignees View on GitHub

@zacjansheski is already working on this.

Since Jun 17, 2025.

needs review percussion UI
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UI bug (incorrect info or interface appearance)

Description with steps to reproduce
  1. Open/create a score with a percussion staff, open the piano keyboard panel
  2. Make sure that the "Use legacy percussion panel" setting is deactivated in the program settings
  3. On the percussion staff, select a note, rest, or highlight the percussion staff itself
  4. The percussion panel will not appear

https://github.com/user-attachments/assets/e05a44b2-3b17-4472-b23e-52c71002d983

Supporting files, videos and screenshots

See above

What is the latest version of MuseScore Studio where this issue is present?

4.5.2 251141402, revision: ac9d3bc

Regression

I was unable to check

Operating system

Windows 11

Additional context

The percussion panel will appear if I switch either from MS Basic to MuseSounds or from MuseSounds to MS Basic.

This behaviour was intentionally introduced with #26807 as a means of resolving #23676, but the logic could probably be smarter.

https://github.com/user-attachments/assets/b812c930-0238-420c-aa75-c0d21d07520a

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

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.