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 #277090: reset tempo only for the relevant range on layout #4080

Merged
merged 1 commit into from Oct 31, 2018

Conversation

dmitrio95
Copy link
Contributor

This pull request fixes an issue with playback tempo change on editing certain parts of a score. This happened because tempo map is cleared on layout and is then rebuilt from scratch, though only for the layout range. This patch makes tempomap be reset only in the layout range too thus preventing loss of tempo information leading to unwanted playback tempo behavior.

@@ -71,6 +71,8 @@
#include "breath.h"
#include "instrchange.h"

#include <limits>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't this more a candidate for all.h? #include <limits.h> is in there already

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't know that all.h contains also includes from C++ standard library. Yes, then this include is not necessary here.

@anatoly-os
Copy link
Contributor

Some tests are failing

@Jojo-Schmitz
Copy link
Contributor

Jojo-Schmitz commented Oct 30, 2018

I believe those failures are due to @wschweer's afd4c43, completly unrelated to this PR

@anatoly-os anatoly-os merged commit 18a900b into musescore:master Oct 31, 2018
anatoly-os added a commit that referenced this pull request Oct 31, 2018
fix #277090: reset tempo only for the relevant range on layout
@dmitrio95 dmitrio95 deleted the 277090-tempo-reset branch June 19, 2019 08:20
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

3 participants