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

Breaking up beamed notes when changing note duration does not show flag until further edits are made #20358

Closed
zacjansheski opened this issue Dec 7, 2023 · 5 comments · Fixed by #21156
Assignees
Labels
engraving P2 Priority: Medium regression MS4 Regression on a prior release

Comments

@zacjansheski
Copy link
Contributor

zacjansheski commented Dec 7, 2023

Issue type

UX/Interaction bug (incorrect behaviour)

Bug description

Changing a beamed eighth note to sixteenth, or a similar action, will not produce the correct flag.

Steps to reproduce

  1. Create a score and add a bar of eighth notes
  2. Change an eighth note to a sixteenth
  3. It will look like a quarter note (no sixteenth flag). rests appear correctly
  4. Switching to a different page view or making another edit in the score will correct the issue

Screenshots/Screen recordings

video1936010878.mp4

MuseScore Version

OS: macOS 14.1, Arch.: x86_64, MuseScore version (64-bit): 4.3.0-233410302, revision: github-musescore-musescore-efbc260

Regression

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

Operating system

Mac OS 14

Additional context

This worked correctly in 4.1.1

@muse-bot muse-bot added regression MS4 Regression on a prior release UX/interaction labels Dec 7, 2023
@zacjansheski zacjansheski added the P1 Priority: High label Dec 7, 2023
@zacjansheski zacjansheski changed the title Continuous view flag changes don't appear until further edits Breaking up beamed notes when changing note duration does not show flag until further edits are made Dec 7, 2023
@zacjansheski
Copy link
Contributor Author

It is actually more fundamental than my original report. Notes just need to be beamed for the bug to occur

video1842948870.mp4

@zacjansheski zacjansheski added P0 Priority: Critical and removed P1 Priority: High labels Dec 7, 2023
@zacjansheski
Copy link
Contributor Author

This is a really recent regression, doesn't happen in the build from 3 days ago

@Eism
Copy link
Contributor

Eism commented Dec 8, 2023

the first bad commit 34fb37b

@Eism
Copy link
Contributor

Eism commented Dec 8, 2023

Removed from the 4.2 project because the problem commit was merged only to the master

@Eism Eism assigned igorkorsukov and unassigned Eism Dec 8, 2023
@oktophonie oktophonie assigned miiizen and unassigned igorkorsukov Jan 12, 2024
@oktophonie oktophonie added P2 Priority: Medium and removed UX/interaction P0 Priority: Critical labels Jan 12, 2024
@sammik
Copy link
Contributor

sammik commented Jan 12, 2024

I think this one #20864 is the same.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engraving P2 Priority: Medium regression MS4 Regression on a prior release
Projects
Development

Successfully merging a pull request may close this issue.

7 participants