Sadly the intentional change is unusable for me. Could it be reverted, or an option be made to ignore the modifier? Or, can it be fixed so it doesn't double press?
Allowing an option to ignore the modifier would be best, as without it, I would not be able to set enough hotkeys to perform actions that I perform with my mouse, which would thus completely break Musicbee for me.
For example, on my Musicbee install at home, I have:
- A dedicated play/pause button on my keyboard that I need to be able to use in conjunction with:
- the shift+mousewheel hotkey via X-MouseButtonControl, in addition to:
- Ctrl-F7 that I use when I have multiple media players open at once and want to only control Musicbee specifically.
- As well, I use a modifier button on my mouse that presses F18, to hold F18 and then press mousewheel (aka, F18+mousewheel) to pause the music using just the mouse.
- I also have a secondary keyboard I use with AutoHotKey that is wrapped around the F24 modifier key, to press spacebar on it to pause.
- As well, I have a modifier key on my main keyboard wrapped around F13 which allows me to use spacebar to pause (F13+spacebar)
- And finally, I have a footpedal also handled by AutoHotKey where the middle foot button pauses.
Even if the double input issue is fixed, I would still need to be able to assign multiple hotkeys to perform the same action (in this case, Play/Pause) in order to restore functionality to all of the methods I use to pause the music that I outlined above.
This is why I think having an option to ignore the modifier is crucial. As it stands, it is a massive accessibility issue that severely hinders the way I and others use Musicbee. With the current implementation, I would lose access to all these methods I use just to pause Musicbee. Consequently, these hotkeys will continue to work for every other application, except for Musicbee.
Topic: Hotkeys no longer work when another modifier is held (Read 414 times)