musescore/MuseScore

Replacing a stave spacer with another is not undoable

Open

#34,423 opened on Jul 31, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)C++ (2,432 forks)batch import
P3UX/interactioncommunitygood first issue

Repository metrics

Stars
 (11,122 stars)
PR merge metrics
 (Avg merge 9d 4h) (153 merged PRs in 30d)

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

Dragging a stave spacer on top of another of a different type replaces the original spacer correctly, but Undo removes any spacers rather than reinstating the original.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/377e8a9e-92d1-48c0-8978-ca1d639bffb9

In which versions of MuseScore Studio is this issue present?

Latest main

Regression

No.

Operating system

macOS 26.5.2

Additional context

No response

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

Research direction
Inspect the undo mechanism for stave spacer actions. Trace the code path that replaces one spacer with another and check how it records the previous state. Search for tests related to spacer undo behavior.
Tech stack
cpp
Domain
desktop
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitC++
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65