musescore / musescore/MuseScore

Pasting across the final barline makes two final barlines instead of pushing it to the end of the score

Open
#27,217 4 comments 0 reactions 2 assignees View on GitHub

@miiizen is already working on this.

Since Mar 26, 2025.

MusicXML needs info 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. Copy a group of measures.
  2. Paste it at the end of the piece so that you're pasting more measures than there are left.

Current behaviour: the old final barline stays wherever it already was. The copied measures are pasted across it, making the piece longer and placing a second final barline at the end of the pasted measures. Which results in two different final barlines: one where the piece formerly ended, and another one where it currently ends.

Expected behaviour: the pasted measures push the final barline so that it's at the end of the (now longer) piece.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/d3cc1ed5-8288-45c8-901e-d69d25e27962

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

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

Regression

I was unable to check

Operating system

macOS 14.5 (23F79)

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

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.