When putting a line in a note for the first time...

• May 23, 2020 - 17:40

...and you press left or right arrows, then, only for the first time, pressing just them should act like pressing left/right + shift. What I tell is that there will be no need to press spaceshift the first time you put a line with "s" for example, because I believe it can be fast. And afterwards shift button will be required.


Comments

It'll never be faster than selecting the correct range to begin with. Or for some line types (such as the slur from your example) to simply enter them during note entry.

In reply to by [DELETED] 32872726

By mouse or by keyboard, yes. https://musescore.org/en/handbook/lines#apply_lines
And for slurs specifically, entering them during note input is by far the easiest method: https://musescore.org/en/handbook/slurs#note-input-mode

I don't think using just the arrows will be faster than having to hold shift alongside them. The keys are very close to each other on the keyboard, so it doesn't change hand movement at all.

What I am concerned with is that it will completely break normal navigation with the arrow keys, preventing me to add a line and then move on to do other stuff. If the line was added over the correct range to begin with, you would now force me to do other stuff before being able to resume normal keyboard navigation.

I'm against this proposal because imho it doesn't add any value but breaks important functionality for no apparent reason.

In reply to by [DELETED] 32872726

Ah yes, true that arrows change position after adding an element, just like they do on any other element. For example after having added a dynamic they allow me to alter the position of that dynamic; not it's anchor point.

I still believe changing the behaviors for arrows for lines only in the case when adding them and not when editing them after the fact is a bunch of special casing and not worth braking consistency for. From a technical point of view though, when you "add" the line, it is added and subsequently placed into edit mode. For MuseScore there is currently no way of knowing that that edit mode happened because the line was added, or because you put it into edit mode yourself at a later time.

Having a command (arrow keys) behave differently depending on when/why something was put into a mode that otherwise and for all elements behaves otherwise the same needs a very good reason imho.

Do you still have an unanswered question? Please log in first to post your question.