musescore / musescore/MuseScore

Feature Request: Easier way to swap vertical stacking order of Chord Symbols and Voltas (1st/2nd endings)

Open
#31,979 4 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

Description: Currently, MuseScore Studio defaults to placing Chord Symbols closest to the staff, with Volta brackets (1st/2nd endings) placed above them. In many engraving styles, it is preferred to have the Volta brackets closer to the staff and Chord Symbols positioned above the brackets.

OS: Windows 11

MuseScore Version: MuseScore Studio 4.6.5

Problem to be solved

The Current Pain Point: Achieving this custom layout is extremely difficult and time-consuming. My current workaround is:

Prior art

1.Select all Chord Symbols in the system.
2.Disable "Auto-placement" (or "Exclude from vertical alignment") in the Properties panel.
3.Manually move Chords extremely high.
4.Move the Voltas down to the staff.
5.Manually readjust the height of the Chord Symbols to sit just above the Voltas.
6.This manual process is labor-intensive, especially for long scores, and breaks easily when the layout changes.

Image
Additional context

Suggested Solution:

Prioritization Setting: Provide an option in the Style settings to change the vertical stacking priority (order) for specific element types.

Easier Swapping: Improve the "collision avoidance" logic so that dragging one element past another vertically allows them to "swap" positions more intuitively without having to disable auto-placement for everything.

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.