musescore / musescore/MuseScore

Mode-specific settings for enabling/disabling automatic score panning

Open
#23,901 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request needs design approval needs review
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Your idea

I would like to have settings for enabling and disabling automatic panning/scrolling of the score, separated by what mode the application is in, roughly like this:

  • Allow automatic canvas movement in input mode
  • Allow automatic canvas movement during playback
  • Allow automatic canvas movement when not in input mode or playback
Problem to be solved

I sometimes work in blocks where I fill only a couple of bars instrument by instrument, and align the bar lines just inside the viewport. Every time I've completed one instrument, the canvas is yanked away because the next bar (where the next input note would be) is not completely visible.

This can be quite disorienting and annoying. I understand why this is the default behavior but would like to have a setting to override it.

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.

Research direction

The issue names no files, tests, or entry points. Start by locating the existing automatic score panning or scrolling preference and the input, playback, and non-input/non-playback modes. Done means separate settings exist and automatic movement follows each setting in its corresponding mode.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.