Option to re-enable double clicking?
The latest major update changed a lot of functionality that originally required a double click to activate to now only require a single click. While I like this for things like adding elements to the score from a palette, there are some areas where I find this very frustrating and I really just wish there was a way to revert to the old double click input system but as far as I can tell this is no longer an option.
The thing that I have found most frustrating with the new single clicks is switching between instruments during note input in a percussion/drumset part. Previously, you could single click on an instrument and it would play the sound without adding it to the score. I found this very useful because it allowed me to browse through the sounds to decide which one fits best or if I just don't remember what instrument it is but now single clicking will automatically add it to the score. The worst part is that if you have a time selected where you already have a note inputted it will delete that note and replace it with the new one. This makes it very frustrating when you are trying to have multiple percussion instruments or drums play at the same time and almost impossible to input a drumset groove in an intuitive way. When I am inputting a drumset part I like to put all of the hi hats and then go back and add the snare and bass any anything else but with this new system it keeps deleting the hi hats when I switch to snare or bass.
I would appreciate an option to go back to double clicks or even the ability to set whether you want to use double or single clicks for different features.
Comments
single click for drum entry will get disabled in 3.4.2 again
See also discussion in https://musescore.org/en/node/300139
Indeed, this was an oversight for drums that causes loss of functionality, so that aspect of the change will be reverted.
But as far as we know there are no other areas where there are any problems due to single-click replacing double-click - it merely saves a click. So unless you have any other specific example we need to investigate, there shouldn't need to complicate things further with more options. We just need to fix the drum palette, and plan to have an update out very soon.
Some observations/questions:
"The worst part is that if you have a time selected where you already have a note inputted it will delete that note and replace it with the new one."
Isn't that how it already operated? In 3.3.4, when pressing Note-Entry, if there's a note already there at the note-entry slot, if you double-click from the drum palette, the hit replaces the the previous 'note'. Or maybe I'm missing something. Only keyboard entry seems to regard voices and also the "add to chord" [shift] functionality.
So also with "with this new system it keeps deleting the hi hats when I switch to snare or bass." it seems to me that this is already how it is: i.e. in 3.3.4, if you insert hi-hats via palette entry, start at the beginning and double-press a kick, it will erase the hi-hat. You need multiple voices which don't work with palette-entry clicking but with keyboard entry as it is. Or you need chord-building which doesn't work without the keyboard+shift. Again,... unless I'm missing something.
As an aside, after reverting to double-clicking again, maybe single-clicking can be implemented appropriately with the addition of a "Sound Preview" option that can be checked off or on so that upon hovering over drum palette items, a sound preview occurs? If that were implemented, would that fulfill the desire for double-clicking the palette? That with the addition of enabling [shift+single click] for "chord"-building might be an appropriate method.
In reply to Some observations/questions:… by worldwideweary
Prior to 3.3.4, that is how double click worked, yes. But the point is, you could build chords (and do other useful things) by single clicking in the palette, then clicking in the score. That was a pretty common way people would use the palette, and that what is lost right now. But the PR to restore that behavior was just merged, so it should be appearing in the next update soon.
In reply to Prior to 3.3.4, that is how… by Marc Sabatella
Right on. Thanks for the clarification.
I was surprised to find that when I clicked on a tie to (x) alter position, the handles came up. However I discovered that the function still worked, only waited until I exited the selection. I assume this is consistent.