musescore / musescore/MuseScore

Explode always explodes entire bar

Open
#34,299 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs design 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)

Description with steps to reproduce
  1. Select a chord on the last beat in a bar
  2. Explode

Expected: the last beat in this staff and the ones below it are affected.

Actually: the whole bar is affected, as if I had selected the whole bar first.

Supporting files, videos and screenshots
Image Image
In which versions of MuseScore Studio is this issue present?

OS: macOS Sequoia (15.7.7), Arch.: arm64, MuseScore Studio version (64-bit): 4.7.4-260706075, revision: github-musescore-musescore-7688c00

Regression

I was unable to check

Operating system

macOS

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.

Research direction

Reproduce the issue in MuseScore Studio 4.7.4 by selecting a chord on the last beat and choosing Explode. Trace the Explode command's selection handling, then verify that only the selected last beat and the corresponding lower staves are affected rather than the entire bar.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.