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 #292343: measure numbers restart from 1 after section break even if the corresponding property got disabled #5427

Merged
merged 1 commit into from
Nov 1, 2019

Conversation

Harmoniker1
Copy link
Contributor

@Harmoniker1 Harmoniker1 commented Oct 28, 2019

Resolves: https://musescore.org/node/292343.

Some calls of sectionBreak() should be changed to sectionBreakElement() so the property can be accessed by sectionBreakElement()->startWithMeasureOne().

@Harmoniker1 Harmoniker1 changed the title fix #292343: measure numbers restart at 1 after section break even if the corresponding property got disabled fix #292343: measure numbers doesn't restart from 1 if the relevant property is disabled Oct 28, 2019
@dmitrio95
Copy link
Contributor

In 2.3.2 MeasureBase::sectionBreak() directly returns LayoutBreak* so adjustMeasureNo() and doLayout() can access the property of that LayoutBreak. But now it returns bool

Why not to use sectionBreakElement() then?

@Harmoniker1
Copy link
Contributor Author

Why not to use sectionBreakElement() then?

Ouch! Guess I really need to study the code more carefully :o

@Harmoniker1 Harmoniker1 changed the title fix #292343: measure numbers doesn't restart from 1 if the relevant property is disabled fix #292343: measure numbers restart from 1 after section break even if the corresponding property got disabled Oct 28, 2019
…if the corresponding property got disabled

Some calls of `sectionBreak()` should be changed to `sectionBreakElement()` so the property can be accessed by `sectionBreakElement()->startWithMeasureOne()`.
@dmitrio95 dmitrio95 merged commit 55e7598 into musescore:master Nov 1, 2019
@Harmoniker1 Harmoniker1 deleted the section-break branch November 1, 2019 09:29
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