musescore / musescore/MuseScore

Expanded options for adding horizontal frame

Open
#31,302 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

I sometimes wish to have a right-margin indent — for example when there’s a DS or DC, or in a final system that has only a few measures. It would be useful to be able choose whether to add a frame before or after a selected measure — such that frames added after a measure would not override a system break set for the measure the frame is added after.

Problem to be solved

Adding frames to create a right margin indent — for section breaks, short final systems, whatever — requires a two-or-more-step process of adding the frame to the following measure, pushing it up to the previous system, adding a break, etc.

Prior art

No response

Additional context

Measures can be added before first measure or selected measure, or after selected measure or last measure. Frame-adding having the same options seems to me to be consistent behavior.

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.

Research direction

No files, tests, or entry points are named. Start by locating the existing command for adding horizontal frames and the measure-insertion actions, then trace how selection and system breaks are handled. Done means frames can be added before or after the selected measure, including after the last measure, without overriding a break on the following measure.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.