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

Commits rebased from 3.x #6379

Merged
merged 7 commits into from
Jul 29, 2020
Merged

Conversation

Harmoniker1
Copy link
Contributor

@Harmoniker1 Harmoniker1 commented Jul 28, 2020

From #5773, #6122, #6240, #6265.

@Harmoniker1 Harmoniker1 force-pushed the rebased-PRs branch 6 times, most recently from b065469 to c0e01da Compare July 28, 2020 08:24
@Harmoniker1
Copy link
Contributor Author

Code style check passed (the existing errors are not from this PR)

@igorkorsukov
Copy link
Contributor

Code style check passed (the existing errors are not from this PR)

Try to rebase, I've just fixed a number of issues.

…with same duration

This is because it doesn't check whether the time signature is local or not, so it always goes to every staff and trys to find a time signature segment, causing `nullptr`.
…perly

`Pid::LINE_WIDTH` cannot be used, since it's a `qreal` value, but the value used to store the line thickness of an ambitus is a `Spatium` value, so we have to use another `Pid` which is `Spatium` type, a new one `Pid::LINE_WIDTH_SPATIUM`.
This is because the `mag()` factor isn't taken into consideration.

Along with multiplying `mag()` in some places, I also created a new member function `minHeight()` for `Tremolo` class to calculate the effective height of tremolo strokes, that is, the height the strokes spread across a given vertical line, without multiplying `spatium()`, to resolve an issue of stem length (a bit longer than intended when direction is down and has single-note tremolo on it) which is not obvious in normal size but obvious in cue size. Several places are already using this effective height, so a separate function for calculating it is really convenient to use.
@Harmoniker1
Copy link
Contributor Author

@igorkorsukov There's still one codestyle inconsistency you missed :-) I added it to this PR.

@igorkorsukov
Copy link
Contributor

@igorkorsukov There's still one codestyle inconsistency you missed :-) I added it to this PR.

Thanks :)

@Harmoniker1
Copy link
Contributor Author

Harmoniker1 commented Jul 28, 2020

Vtest failures are expected

@igorkorsukov igorkorsukov merged commit 0cac4ec into musescore:master Jul 29, 2020
@Harmoniker1 Harmoniker1 deleted the rebased-PRs branch July 29, 2020 09:27
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.

2 participants