musescore / musescore/MuseScore

Key signature hitbox follows too strictly the key signature shape

Open
#25,284 2 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

P3 UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce
  1. create a score with whatever key sig that isn't C major or the Atonal one
  2. try to select the key sig by clicking in the space between the flats or sharps

Actual behaviour: the measure, not the key signature, is selected.
Expected behaviour: This space is in the range of the key signature, I expect that only the key signature is selected.

Sometimes you move the mouse fast and the cursor is not so precise to target precisely the flats (or sharps) in the key sig every time.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/a32c5474-0837-4d84-8a3b-f4a28257d447

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

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.2-242570931, revision: github-musescore-musescore-3130f97

Regression

I was unable to check

Operating system

Windows 10 Pro

Additional context

I suggest rethinking the hitboxes of this section of the staff, as there are too many blank areas where a click selects the measure.

1
Please notice that if you click a few pixels above or below the time sig, on the staff line, the measure (not the time sig) is still selected.

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.