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

fix #301395: single-note dynamics: decrescendo doesn't work on tied notes with subchannels #6530

Merged
merged 1 commit into from
Oct 5, 2020

Conversation

jthistle
Copy link
Contributor

@jthistle jthistle commented Sep 2, 2020

Resolves https://musescore.org/en/node/301395

The two removed lines had been there since the initial commit. I think conditions had changed significantly and whatever purpose they may have served - my guess is some ill-advised 'optimization' - it seems that that purpose no longer exists. They were certainly the lines causing this issue.

Added a new test too to deal with this scenario.

@jthistle jthistle changed the title fix #301395: single-note dynamics: decrescendo doesn't work on tied n… fix #301395: single-note dynamics: decrescendo doesn't work on tied notes with subchannels Sep 2, 2020
@vpereverzev vpereverzev merged commit aae95c4 into musescore:3.x Oct 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants