Mid-measure keysig changes are not possible anymore

Open
#26,614 1 comment 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

Assessment

This issue has not been assessed yet.

Description

needs review regression MS4 UX/interaction
Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce
  1. In a score select a mid-measure note or rest
  2. In the key signature palette click a key signature

Expected result:
Key signature shows in front of the selected note or rest

Actual result:
Key signature shows in front at the start of the measure

Workaround:
Hold Ctrl while applying the key signature, and repeat that for all staves of the score at the same beat

Supporting files, videos and screenshots

n/a

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

4.1 - 4.6

Regression

Yes, this used to work in a previous version of MuseScore 4.x (namely in 4.0)

Operating system

Windows 11, but that shouldn't matter at all

Additional context

Came up in https://musescore.org/en/node/352208, https://musescore.org/en/node/374313, https://musescore.org/en/node/375352

Regression happened between 4.0.2 (works) and 4.1.0 (fails)

The handbook ( https://musescore.org/en/handbook/4/key-signatures#add-key-sig) mentions:
Note: It is also possible, though uncommon, to add a key-signature mid measure by selecting a note then clicking a palette key signature, or dragging the key signature to a note.

As per https://github.com/musescore/MuseScore/issues/18202#issuecomment-1607906586 this is intentional

If so, the handbook needs to mention that and make the mentioned workaround the official procedure.
However, I'd challange that intention and still call it a bug, at least on the usability side.

The for now on that comment seems to give some hope...

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
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

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.

More from musescore/MuseScore

All issues in musescore/MuseScore

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.