Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Break beam left does not affect the dotted rest #22732

Closed
Dima-S-Jr opened this issue May 9, 2024 · 1 comment · Fixed by #22753
Closed

Break beam left does not affect the dotted rest #22732

Dima-S-Jr opened this issue May 9, 2024 · 1 comment · Fixed by #22753
Assignees
Labels
P1 Priority: High regression MS4 Regression on a prior release UX/interaction

Comments

@Dima-S-Jr
Copy link

Dima-S-Jr commented May 9, 2024

Issue type

UX/Interaction bug (incorrect behaviour)

Bug description

The beam cannot be extended to a dotted rest. Instead, the dotted rest beam type automatically reverts to the "no beam" type.

Steps to reproduce

  1. Enter a dotted rest value of 1/8 or less.
  2. After that, enter the notes with the same value.
  3. Try to extend the beam to a dotted rest.

Screenshots/Screen recordings

06-45-13.mp4

MuseScore Version

MuseScore Studio version (64-bit): 4.3.0-241231433, revision: github-musescore-musescore-5f36e74

Regression

Yes, this used to work in MuseScore 4.2.1

Operating system

Windows 11

@muse-bot muse-bot added regression MS4 Regression on a prior release UX/interaction labels May 9, 2024
@DaddyLudwig
Copy link

I also had an issue with beams and dotted note values, namely that breaking the beam between a pair of eighth notes and a dotted eighth in 2/2 is impossible without setting the second eighth to No Beam. I thought this beaming issue with dotted note values was time signature specific, but I guess it isn't.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 Priority: High regression MS4 Regression on a prior release UX/interaction
Projects
Development

Successfully merging a pull request may close this issue.

5 participants