MS 2.3.2 edit mode: cursar-up/down keys cause note-head microshifts, not pitch change

• Sep 16, 2018 - 03:40

I am using MS 2.3.2 rev 4592407 on Linux Mint 17.3 (kernel 4.4.0-134-generic x86_64). In edit mode, if I select a note, the cursar-up/down keys normally will change the note pitch a half-step at a time. Occasionally something seems to alter the select state so that the up/down keys give micro-increments in the notehead vertical position instead of the normal action. I can usually correct this by selecting something else or clicking on the blank part of the page to clear the selection, then reselecting the note and checking that I hear the sample instrument sound to verify the select.

Has anyone else noticed this behavior?


Comments

I get the same behavior when I accidentally double click the note head instead of single clicking it. You will know you double clicked it when most of the toolbar icons turn gray and the status bar at the bottom right of the MuseScore window has the word Edit in it.

To be clear:

"Normal" mode is what you are in, well, normally. This is the default in MuseScore. In this mode, the arrow keys change pitch.

"Edit" mode is what you are in when you double-click something. In this mode, arrow keys make fine adjustments (or coarser adjustments with Ctrl). And indeed, clicking elsewhere (or pressing Esc) is how you leave Edit mode and return to Normal mode.

In reply to by Marc Sabatella

OK, so that explains it. I suspect that the left-button switch on my mouse is showing some contact bounce, effectively turning a single-click into a double-click - this would also explain some behavior that I've seen in other programs. And thanks, Marc, for the pointer on terminology.

I see from a brief Google search that Linux generally has no software debouncing for mouse-button contacts, although Windows seems to have it built-in. As an engineer who has had to deal with pushbutton inputs to electronic gear, this amazes me.

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