musescore / musescore/MuseScore

Range selection - Layout elements (staff spacer, frame, staff type change, measure) issues

Open
#21,184 0 comments 0 reactions 1 assignee View on GitHub

@avvvvve is already working on this.

Since Jan 26, 2024.

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

Aplying some layot element on range selection gives strenge results.

For breaks, it seems to be correct - adding break to selection adds it befor and after. Adding "keep measures on same system) adds it between each pair in selection.

But other elements I thhink are not correct

  • 1. staff spacers are added to each measure of selection (I would expect only firs measure)

  • 2. staff spacers are added always to top staff of selection (it make sense in spacers up, but not much sense if three staves selected and spacers down) For spacers down, I would expect either adding it only to bottom staff, or adding it between each selected staves.

  • 3. frames, and measures are added to each measure in selection (in Add -> Frame dialog it adds only one before whole selection)

  • 4. staff type change is added to each measure in selection, but only to top staff. (I would expect either only begining of selection, or same behaviour, like breaks have - add one to begining, and second after end of selection. And to each selected staff, not only top one.)

  • 5. If added break, than Undo, adding spacer adds also extra one to measure after selection. See: #17718

Steps to reproduce
  1. select range selection couple measures some inner staves in score
  2. apply Layout elements from palette
Screenshots/Screen recordings

https://github.com/musescore/MuseScore/assets/1646034/83061239-d723-47dc-b8d9-f0563ae37701

MuseScore Version

master

Regression

No.

Operating system

Ubuntu 22.04

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.