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 #222171: cannot enter chord mid-measure in empty measure #3211

Merged
merged 1 commit into from Jun 14, 2017

Conversation

MarcSabatella
Copy link
Contributor

The main issue here is the change in harmonyBeatsTab, we aren't calculating ticks correctly when testing to see if going to the next chordrest segment has overshot the beat. The original calculation was good before a change a few months ago that required the Segment constructor to be called differently (see 4e0b0db#commitcomment-22518030), so I've just update the code to only change the call there rather than changing the meaning of newTick throughout this function.

I also made a fix to cmd(), where the "chord-text" command was actually forcing a change to note input state before entering the chord. This also seems to have been a recent "regression" that was basically an oversight. I don't know that it currently has any bad effect, because we later force a change to edit state. But it does prevent my PR for #3199 from working correctly - it similarly prevents a chord symbol from being added mid-measure in empty measures.

@lasconic lasconic merged commit b2e1636 into musescore:master Jun 14, 2017
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