musescore / musescore/MuseScore

Improve automatic repositioning of score during note input

Open
#25,836 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

When entering the last notes on a page, the paper will immediately jump to the next page. However, this is often unhelpful if someone is trying to write the final note for all staves before moving to the next page.

https://github.com/user-attachments/assets/3837c7b5-53ae-4549-a3f6-117dbdf9a9d1

I suggest that the paper, instead of advancing to the next page, advances to either the half position (as I dragged it over to in the video), or the three quarter position (in which three-quarters of the new page are showing along with one quarter of the first).

Problem to be solved

It is very frustrating to have to drag the paper back manually when I want to finish with all staves before moving to the next measure.

Prior art

No response

Additional context

Though it would solve the problem; I don't like to use continuous view, especially if I am working on a final engraving of a score.

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

Start by locating the score-view repositioning logic used when entering the last notes on a page, then trace how the next page is selected. Compare behavior that leaves the view at the half or three-quarter position, and confirm the chosen behavior while finishing all staves before advancing.

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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.