musescore / musescore/MuseScore

Apply time signature after undo can produce inconsistent results

Open
#24,962 0 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

P2 regression MS3 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)

Description with steps to reproduce
  1. Create a new score with default 4/4 time signature and fill 3 measures with 1/4 notes
  2. Select just the first two measures
  3. Apply a 3/4 time signature from the palette
  4. Note the following (4/4) measure remains as is, with an extra rest inserted in the previous (new) 3/4 measure
  5. Undo - returns to state after step 2. (first two measures selected)
  6. Re-execute step 3 (apply 3/4 time signature)
  7. Expected: should produce same result as seen in step 4
  8. Actual: result is different, with the notes from all 3 measures now spread over 4 3/4 measures followed by an empty 4/4 measure.
Supporting files, videos and screenshots

Start:
image
After first 3/4 apply:
image
After undo and reapply 3/4:
image

What is the latest version of MuseScore Studio where this issue is present?

4.4

Regression

Same in all versions of 4
Regression of MuseScore 3

Operating system

Windows 11

Additional context

Not a major issue, just a weird quirk that may be worth investigating, as anything that means "undo" isn't properly restoring a previous state can potentially lead to more serious problems.

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.