musescore / musescore/MuseScore

Apply Measure Properties only applies some settings to last selected measure

Open
#22,128 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

community 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)

Bug description

If you select multiple measures and bring up the measure properties command, then property changes only apply to the last measure in the selection, even when it would sensible/useful to apply to all.

Steps to reproduce

Select 2 consecutive measures
Right click and choose "measure properties"
Change actual beats per bar (e.g. to 5)
Click OK

Actual behaviour: + to indicate extra beats only shown for second measure
Expected: both measures should have the same property change applied

(Actually my use case was the reverse, an imported file had an extra beat in every single measure. Because of this bug I had to fix them all one by one. Arguably the problem could also be fixed at the xml import stage, but it was a problematic xml file, and at any rate, it's still reasonable to expect if you select multiple measures and change properties it applies to all of them).

Screenshots/Screen recordings

No response

MuseScore Version

4.2

Regression

I don't know

Operating system

Windows 11

Additional context

No response

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

Start by reproducing the issue in MuseScore 4.2 with two consecutive measures selected, then trace the Measure Properties command's handling of multi-measure selections. Done means changing actual beats per bar updates every selected measure, with the reported behavior covered by a regression check.

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
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.