Change interval/chord input behaviour
I'd like to suggest changing MuseScore behaviour when you enter chords or intervals: now (when you are in note input mode) you can add an interval to the existing note by clicking above or below it, while clicking with "shift" key pressed replaces the note with the other one.
I think, it makes sense to change the behaviour to the "opposite" one: clicking with "shift" pressed adds a note to make an interval/chord, and clicking without "shift" pressed - replaces the note with the new one.
That seems to be more logical to me, what do you think about it?
| Attachment | Size |
|---|---|
| scr_new_issue.jpg | 4.28 KB |
Comments
What would the advantage be? Right now, it is easy to create chords (no Shift required). Shift is needed only to correct mistakes basically. Reversing this seems like a step backwards.
In reply to What would the advantage be?… by Marc Sabatella
There is logic to this since keyboard input uses shift to add to a chord and no shift to overwrite a chord. I think with the mouse, the less keyboard interaction would be the better option, that is no shift to add to a chord and press shift to fix a mistake, that is overwrite a note/chord.
In reply to What would the advantage be?… by Marc Sabatella
As I've written, that just seems to be more logical to me - having "note replacement" as the default behaviour, i.e. by default I suspect adding a single tone or replacing it, while making an interval/chord is supposed to be just the second action (in terms of priority), usually linked with "shift+something". And I also agree with the second comment - when inputting from keyboard, we use shift to make chords, so, again, using "shift" with mouse seems more consistant to me because of that. However, I've made this post just to suggest and to see what community thinks about it.
In reply to As I've written, that just… by Alexander T
I don't use the mouse for note input, I use my computer keyboard and I did agree your idea has logic.
Having said that, having the mouse replace a note is only logical on instruments capable of making a single sound at a time. While this is the majority of the instruments listed in MuseScore, it is not what the majority of users do. Most users make music for pianos and guitars, both of which are very capable of playing chords, so it makes more sense for them to have click with no shift add to a chord.
I am now done with my opinion. I'm just explaining why I think the decision was made the way it is.
In reply to I don't use the mouse for… by mike320
thanks for the comments!
In reply to As I've written, that just… by Alexander T
I can see the consistency logic with how keyboard input uses the modifier for adding, but repitching with the mouse is as "easy" as dragging the existing note.
I'm not sure click-to-replace is that much faster than drag-to-repitch, while I'm positive that click-to-add is faster than shift-click-to-add.
In reply to I can see the consistency… by jeetee
Dragging to repitch doesn't work in note input mode. If you try to drag it will add a note where the drag begins. I would say it's faster to press the shift to replace the note than to turn off note input, drag the note, then turn note input back on.
In reply to Dragging to repitch doesn't… by mike320
Ah good point (you now notice how often i use mouse entry...)
Then I think it boils down to whichever action would be taken the most (repitch vs chord entry) to see which one would need the modifier? For me, it can go either way.
In reply to Ah good point (you now… by jeetee
I presented my opinion. I don't use it much either.
In reply to Dragging to repitch doesn't… by mike320
It is even faster to use the cursor keys to move the note to right place.
In reply to As I've written, that just… by Alexander T
Interesting discussion! I agree there is a certain consistency / logic about having Shift add to chord just as with keyboard entry, and that's bothered me a little at times also. But in some cases at least I think discoverability, ease of use, and efficiency are more important. It's going to be much harder for a mouse user to happen upon the discovery that he can add notes to a chord with Shift, whereas there are several ways he can already figure out to change an existing note using using pretty obvious means. And as I mentioned, adding to a chord is more common than replacing a note, so efficiency also favors the status quo.
Throw drum entry into the mix - where there are yet other subtle differences - and I do agree the inconsistency is a bit troubling. But I'm still no convinced this is more important than the other concerns. More discussion is certainly welcome!