Space bar has unnecessary control in mixer
The space bar is our default Start / Stop button for playback.
Allowing the space bar to have any control in the mixer window is a real annoyance for me.
I go up to the mixer and click a mute or solo button, but that have to move my mouse back down to the score, and intentionally click somewhere down there before clicking space bar to start playback.
If I mute or solo something in the mixer, and then mistakenly just hit the space bar, then it just reverts my previous change in the mixer.
It's a major work flow slowdown IMO.
For what possible reason could we want the space bar to work in the mixer?
Please fix!
Thank you!
Comments
The reason is to be able to start and stop playback. Similar to other players
You wrote:
If I mute or solo something in the mixer, and then mistakenly just hit the space bar, then it just reverts my previous change in the mixer.
In MuseScore 4, you will be able to select mute/solo in the mixer, then hit space bar to play immediately (without the mixer reverting the selection).
For what possible reason could we want the space bar to work in the mixer?
For example...
The text in the 'Name' field in the details area of the mixer can be edited to something like 'Trumpet 2' for which a space would be needed (without playback commencing).
In reply to You wrote: If I mute or solo… by Jm6stringer
Good on MS 4!
Yes. Editing text, but once we exit the text field the SB should then be inactive.
Indeed, it's already fixed for MU4, but for the record, yes, this is a known problem in MU3. The issue turns out not to be with Space specifically, but with the way the mute and solo buttons take focus. Buttons shouldn't take focus when you click on them; that's an error with the buttons themselves that is corrected for MU4.
But other controls in the Mixer definitely need Space to work there - the controls that do take focus. Or, for that matter, the mute button and solo buttons themselves if you explicitly put focus there using the Tab key to navigate. Also, things like text fields, spin boxes, and dropdown lists do need to take focus on click. And once a control has focus, it is actually very important for accessibiltiy reasons (making MuseScore usable by those who use the keyboard exclusively, such as blind users) that Space perform its normal function of activating that control with focus.
So again, the issue here is that the mute and solo buttons never should have taken focus on click to begin with. But once a control has focus, it's correct that Space needs to activate it, anything else makes the interface non-accessible to blind users or others using the keyboard exclusively.