musescore / musescore/MuseScore

Consider improvements to adding and navigating between fingering objects

Open
#32,024 2 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

Currently fingering objects are attached to notes rather than chords, and individual fingering indications automatically stack neatly. However, it is also possible to create a multi-line fingering object (still attached to a single note, but indicating fingering for more than one note in a chord). Hitting Enter while inputting fingering creates line breaks, while hitting Space moves to the next notehead in a chord (or lower voice). There is no command to advance directly to the next chord in a sequence.

Consider disallowing multi-line fingering indications. Enter might then move to the next note in a chord (or lower voice), and Space could advance to the next chord in a sequence. This would offer more flexibility and efficiency to navigation, and may be more intuitive.

Problem to be solved

Advantages:

  • Improve efficiency and flexibility when entering fingering indications.
  • Solve inconsistent padding/line spacing between multi-line and stacked fingering objects (see screenshot - MSS 4.6.5).
Image

Possible disadvantages:

  • Often it may be desirable to treat a stack of fingering indications as a single object, e.g. for repositioning. However, for many simple cases the default positioning will be acceptable. Therefore, advantages in the flexibility offered by individual fingering objects to deal with more complex situations may outweigh the simplicity of single multi-line objects.
Prior art

No response

Additional context

No response

Checklist
  • This request follows the guidelines for reporting issues
  • I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests

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.