musescore / musescore/MuseScore

Score repositioning via navigation commands should not require "Pan score automatically" to be enabled.

Open
#20,512 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

Remove linkage between score navigation and panning during playback

Problem to be solved

Currently (and since for ever I think) if you use a keyboard navigation command - for example CTRL+End to move to the end of the score - or if you use the CTRL+F find function - or if you try to move to a location by selecting an item using the time line function, the score is only repositioned if "Pan score automatically" is enabled in the playback settings.

This linkage between commands to navigate the score (not during playback) and a playback setting is not obvious to users and is rather illogical. The navigation commands should always work whether the score pans automatically during playback or not.

Prior art

No response

Additional context

See also https://musescore.org/en/node/330598

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 tracing the keyboard navigation commands, Ctrl+F find action, and timeline item selection described in the issue, then inspect how each consults the playback setting "Pan score automatically." Done means these non-playback navigation actions reposition the score regardless of that setting; the issue names no files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
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.