musescore / musescore/MuseScore

Wrong hover area for leftmost string of fretboard diagram

Open
#25,575 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

P4 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

Markers can be entered by clicking in the area to the left of the fretboard diagram editor in Properties. This space should not be interactive.

Match the hover area to its size on the other strings.

image

(Reported by @scorster here: https://musescore.org/en/node/369433)

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

Nightly

Regression

No.

Operating system

macOS 15.1

Additional context

No response

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.

Research direction

Start by reproducing the issue in the fretboard diagram editor in Properties on macOS, focusing on the leftmost string and comparing its hover area with the other strings. Trace the editor's interaction handling and identify the relevant source and test locations. Done means the left-side space is not interactive and the leftmost string's hover area matches the others.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.