musescore / musescore/MuseScore

Undo doesn't restore page re-layout (amount of systems on page) after reverting one action

Open
#23,406 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Bug description

After certain operations that decrease the number of systems per page, undo does not restore the score to its previous state

Steps to reproduce
  1. Create score from String orchestra template
  2. Make sure page size is A4 (or change it to A4 in Right click on empty space>Page settings>Page size ) - score by default should show 3 systems per page
  3. Add C note to Violas staff
  4. Move that note several octaves higher with Ctr/Cmd+Up arrow until the first page increases to 2 systems
  5. Undo one time - the note goes back to previous place, but the page still has 2 systems

You should Undo several times until that note disappears

Expected: The pages should restore to 3 systems state after the first Undo

Screenshots/Screen recordings

https://github.com/musescore/MuseScore/assets/90187801/098116b6-9495-4ca0-9b68-4ff0ccfc3e65

MuseScore Version

4.4

Regression

No

The same in 4.0 and 3.6.2

Operating system

Windows 11

Additional context

No response

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 reproducing the undo scenario in MuseScore 4.4 using the String orchestra template, A4 page size, and the octave-moved viola note. Trace the undo operation and page re-layout state; done means the first undo both returns the note and restores three systems per page.

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.