Acessibility option: Mouse-only zoom

• Sep 9, 2021 - 14:48
Reported version
Ergonomical (UX)
S5 - Suggestion

Please consider adding an option to assign a different modifier key to mouse zoom, other than Ctrl, including the ability to set it to none (so that the mouse wheel zooms without any key pressed). Most modern software have that option, including Inkscape, Gimp, Krita...

Navigation is one of the most frequent actions while using MuseScore, it should be possible to do it with the mouse only, as well as entirely with keyboard. Moving around is possible with a mouse (both left click and middle click have the same function, perhaps redundantly), but zooming is not and requires the use of the other arm.

Adding this option would significantly benefit people who have impaired movement in one or both hands and have difficulties use the keyboard and the mouse at the same time. It would also be very useful to people who are just used to a different workflow and use Alt, or Shift to zoom, like in some proprietary software.


Workaround Yes No

Right now, the way to zoom with mouse only would be the dropdown menu on the toolbar. How about just adding +/- buttons to that?

In reply to by Jojo-Schmitz

Workaround Yes No

The suggested workaround (using the zoom drop-down in the main toolbar) is incomplete. The zoom levels are very far apart, for example, there is nothing between zoom 400% and 800%. Zooming to, say 600% is impossible with mouse only, and often necessary in any workflow.

The drop down is useful for resetting the zoom level, but is certainly not sufficient as the only means to zoom with mouse.

Workaround No Yes

It is a workaround none the less (and only one of several), also that field allows for entering any number (but yes, that needs the keyboard)

In reply to by Jojo-Schmitz

How is it a workaround if entering a number requires using the keyboard?

My whole complaint is based on the fact that constant switching between using a mouse and using a keyboard (for people who cannot use both at the same time) is not at all ergonomic. Your suggested workaround does not address that in the slightest.