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 #22917 - Previous fix actually disable precise bar line editing #836

Merged
merged 1 commit into from
Apr 15, 2014
Merged

Fix #22917 - Previous fix actually disable precise bar line editing #836

merged 1 commit into from
Apr 15, 2014

Conversation

mgavioli
Copy link
Contributor

Fix #22917 - Previous fix actually disable high-precision bar line editing.

When editing is exited, an (extra?) final call to BarLine::endEditDrag() is made after the last drag: it was finding shiftDrag turned off by the last call and forced the bar line extrema to coarse precision.
See http://musescore.org/en/node/22917#comment-99269

Fixes:

  • resetting shiftDrag moved from endEditDrag() to endEdit();
  • added a test at the beginning of endEditDrag() skipping it, if there is no drag.

Also fixed:

  • a test for shiftDrag swapped with !shiftDrag
  • an assumption that staves always have 5 lines.

…ne grips.

When editing is exited, an (extra?) final call to BarLine::endEditDrag() is made **after** the last drag: it was finding shiftDrag turned off by the last call and forced the bar line extrema to coarse precision.
See http://musescore.org/en/node/22917#comment-99269

Fixes:
- resetting shiftDrag moved from endEditDrag() to endEdit();
- added a test at the beginning of endEditDrag() skipping it, if there is no drag.

Also fixed:
- a test for shiftDrag swapped with !shiftDrag
- an assumption that staves always have 5 lines.
@lasconic
Copy link
Contributor

Thank you for looking into this.

lasconic added a commit that referenced this pull request Apr 15, 2014
…s_fix

Fix #22917 - Previous fix actually disable precise bar line editing
@lasconic lasconic merged commit 1cfa954 into musescore:master Apr 15, 2014
@mgavioli mgavioli deleted the fix_22917_regression_in_previous_fix branch April 15, 2014 16:08
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