musescore / musescore/MuseScore

When a dynamics change causes a change of hairpin, two undos are required to return to previous state

Open
#27,148 0 comments 0 reactions 1 assignee View on GitHub

@cbjeukendrup is already working on this.

Since Mar 18, 2025.

P3 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

It's arguable whether this is a 'bug' at all, but it's at least an observation.

  1. Start with a p < f

Image

  1. Select the f and, from the dynamics popup, change it to pp; the hairpin will switch from < to >

Image

  1. Press Ctrl+Z to undo. This undoes the change of hairpin, but not the change of dynamic:

Image

  1. Press undo again; this will also change the dynamics back:

Image

Obviously the two changes (dynamics and hairpin) are treated as two items on the undo stack, but it would feel more natural, at least to me, if they were reverted with a single undo, because only one of the actions was explicitly done by the user and the other is automatic (so is, in effect, part of the same action).

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

OS: Arch Linux, Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.0-250721848, revision: github-musescore-musescore-7c55023

Regression

No.

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.