musescore / musescore/MuseScore

Impossible to define the next note duration to a dotted duration when the setting "Apply accidentals, ..." is set to "previous note entered"

Open
#27,907 1 comment 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

needs review regression MS4 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

When entering Input mode, pressing "4" and then "." should define the duration of the next notes to be dotted eight.

Although when the new setting "Apply accidentals, augmentation dots" is set to "previous note entered", it doesn't work any more: pressing "4" changes the duration of the next notes to eight note, but pressing "." adds a dot to the note below the cursor and longer changes the duration to the next notes?

It is de facto no longer possible in that mode to define, with the keyboard, a default dotted duration for the next notes.

That new option was meant to bring back to behaviour of MU3.6 about the "w" and "q" shortcuts as discussed in https://github.com/musescore/MuseScore/issues/24537. If activating that option allows indeed to have "w" and "q" acting such as in MU3.6 it breaks the behaviour of ".".

Supporting files, videos and screenshots

Image

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

4.5.1, 4.5.2

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

Windows 10

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.