Dragging bar lines to top or bottom staff lines requires extra precision
Windows 7, GIT commit: eee9f5f
1) create score for two flutes
2) double click a barline on top staff, drag handle to bottom staff, release anywhere but exactly on the bottom line of the bottom staff
Result: barline extends to wherever you released, which might be a too short or too long
Expected result: barline extends exactly to the bottom of the staff regardless of release point
I'm guessing maybe there was a deliberate change to allow barlines of arbitrary length, but there's got to be an easy way to extend barlines through staves that doesn't require magnifying the score to 400% and very carefully releasing exactly on the right spot. Or maybe there is a way but it's changed?
Comments
It is a deliberate change to allow bar lines starting and ending at several spots across a staff and between staves (in practice every half space from 2 spaces above to 2 spaces below each staff).
It is true that additional precision is required than it was the case with ver. 1.3.
Suggestions for an interface for speeding up the most common cases are welcome.
(Incidentally, setting bar lines is usually done only once for each score, isn't it?)
Thanks,
M.
Indeed, it's a do it and forget it operation, usually at most half a dozen such operations on a score even for large orchestra scores. Whereas I take it these finer adjustments might be the sort of thing where if you need it once, you need it a hundred times. I get that. Something like Shift-Drag or Ctrl-Drag to get the old behavior seems like an obvious candidate - plays off the similar constrained dragging for freely movable elements. Although there will be still be the surprise / discoverability factor that might lead one to say it should be the other way around: keep ordinary drag as it was, require shift or ctrl for the new behavior. I have a sense that more people will be creating scores that want the simple extend-all-the-way-through-staves behavior than will want any sort of fine tuning of barline length. But again, I have no problem accepting that for those who *do* want the latter, they'll likely use it a lot more than the rest of us will want the former.
I would prefer to have the old behavior on drag. And a modifier for the new (and more rare) one.
I just ran into this in testing, and agree that the old way of dragging and snapping to a position should be the default.
Fixed in ecd6222e20
As I proposed earlier, the default is now to snap to staves. To achieve line precision, the user needs to use the Shift key while dragging. And Ctrl is used to modify a single barline.
[Shift] + dragging does not seem to work: top bar line end always snaps to top staff line and bottom bar line end always snaps to bottom staff line.
Looking into it...
M.
PR pushed on Github: //github.com/musescore/MuseScore/pull/836 .
Waiting for Travis to say yes...
M.
Fixed in f23a9f05d0
Automatically closed -- issue fixed for 2 weeks with no activity.