Slur across measures with whole notes causes and editing glitch in a score
This problem is a bit of a nuisance, but still would be nice to fix.
I found this in 2.0 NB 255eaaa, Mac OS X 10.10.1
Procedure:
1. Create three straight whole notes with different notes across the three measures.
2. Select the first note in the sequence.
3. Drag a slur/tie line to the first note. As usual it connects to the second note with the edit handles showing.
4. Drag the rightmost blue positioning square of the slur towards the third note (you can see the circular anchor connected to the second note).
5. While doing this, the right endpoint of the slur suddenly jumps up to the top of the score.
6. You must then drag down the right endpoint all the way to the stave you are trying to work with.
I included screenshots that show what happened during the above steps. Like I said, it is an inconvenience, but if you have a big score with lots of staves this does cause a lot of scrolling.
Thanks!
| Attachment | Size |
|---|---|
| Screen Shot 2014-12-02 at 5.58.00 PM.png | 9.76 KB |
| Screen Shot 2014-12-02 at 5.58.15 PM.png | 12.7 KB |
| Screen Shot 2014-12-02 at 5.58.29 PM.png | 52.29 KB |
Comments
Definitely looks like a bug, but are you aware dragging is not the proper way to extend a slur? You're supposed to use shift + left/right arrow keys. So what you are seeing should not normally be an issue.
OK, I will try that method. Although if the method I used was not "proper", there shouldn't be hotspots to drag it :-)
The handles are mostly for adjusting the *shape* of the slur once you've extended it to cover the notes you want using shift+arrow. That's the way it's always worked in 1.3. But fairly recently the feature of also being able to extend the slur by dragging was added, so we should definitely fix the bug that keeps it from working well.
This issue occured on November 6
- On the last Nightly on November 5 (same behavior with Beta1), it is "correct" (in the sense that you may extend by dragging the slur): https://github.com/musescore/MuseScore/commit/0ff91aa56bbf786102fbf9744…
![1 november5.jpg]( "1 november5.jpg")
- The issue appears the next day, in two steps.
1) First step: on this Nigthly: https://github.com/musescore/MuseScore/commit/5ed2bc8be843beee43497e416…, you see that firstly:
AND THEN, by extending:
2) Second step: the "jump" appears on this Nightly: https://github.com/musescore/MuseScore/commit/fd82ab6679dd88a535cb09d41…
- I add a minimal file for testing: extend.mscz
Fixed in 68a54f76a0
Automatically closed -- issue fixed for 2 weeks with no activity.