-
Notifications
You must be signed in to change notification settings - Fork 409
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable/disable modulation edit mode via forward/back mouse buttons #7982
Comments
what are 'forward back mouse buttons'? a re-click on a modulator arms it for me as does option-a (which is re-selectable in the keyboard mapping). |
forward back mouse buttons are the side mouse buttons you usually use for example in web browser for forward/back navigation: https://user-images.githubusercontent.com/24459435/81587407-48543d80-93b7-11ea-9c11-bcfbfa72ecca.png In original Surge VST this was a very nice feature so that you can enable the modulation mode with the mouse cursor at other location. |
Oh right the 'button4/button5'. It was one of the things we lost access to when we ported to JUCE. Unfortunately JUCE only supports mouse devices with 3 buttons, so we don't have access to those click events. I'm going to have to close this as a 'cant do'. |
Too bad |
yup. we got 9000 improvements and lost one, basically. I'll open a note on the juce forum and link it here to see if there's any hope. |
Thank you! |
Frankly this is not a big deal. Just use middle mouse button instead. |
I don't like clicking the mousewheel |
Well, that's a choice. But as it stands, we cannot bring back support for buttons 4 and 5, so... |
yup lets see if the forum folks have any ideas. |
Yup as suspected forum folks say forking juce is the only answer |
Surge XT V1.3.4 Clap / Windows 11 / REAPER 7.33
-> select any modulator
-> click forward/back mouse buttons
Result: Nothing happens
Expected: Modulation edit mode is enabled/disabled for the selected modulator (this was working this way in the original Surge VST if I remember correctly)
The text was updated successfully, but these errors were encountered: