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 #281866: fix inability to correctly set loop markers in parts #5340

Merged
merged 1 commit into from
Sep 24, 2019

Conversation

dmitrio95
Copy link
Contributor

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

As playback is currently always performed for MasterScore, it would be logical to store the information about positions of playback cursor and loop markers in MasterScore rather than individual excerpt scores. This commit implements this approach and fixes the issue with inability to set loop markers from parts. Strictly speaking, only changing Seq::setLoopSelection is absolutely necessary to fix the issue, the approach with moving _pos to MasterScore allows to naturally avoid incorrect visual feedback due to markers positions information being not synchronized across scores and ScoreViews.

As playback is currently always performed for MasterScore, it would be
logical to store the information about positions of playback cursor and
loop markers in MasterScore rather than individual excerpt scores.
This commit implements this approach and fixes the issue with
inability to set loop markers from parts. Strictly speaking, only
changing Seq::setLoopSelection is absolutely necessary to fix the
issue, the approach with moving _pos to MasterScore allows to naturally
avoid incorrect visual feedback due to markers positions information
being not synchronized across scores and ScoreViews.
@MarcSabatella
Copy link
Contributor

I don't know if the code overlaps or not, but see also https://musescore.org/en/node/148311, which was an issue in 2.3.2 as well and the personal pet peeve of an associate of mine.

@anatoly-os anatoly-os merged commit 82bdcb8 into musescore:master Sep 24, 2019
@dmitrio95 dmitrio95 deleted the 281866-loop-in-parts branch September 24, 2019 07:37
@MarcSabatella
Copy link
Contributor

So this does fix that other issue? Sorry if it wasn't clear, I wasn't suggesting I had tested that.

@dmitrio95
Copy link
Contributor Author

No, the other issue is not related to the one fixed by this PR.

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.

3 participants