darktable
darktable copied to clipboard
Disable Tone Equalizer mouse controls by default
Is your feature request related to a problem? Please describe.
I have only ever used the scroll wheel controls of the tone equalizer module by accident (and I accidentally do it at least once literally every single time I edit a photo), and it also for some reason prevents click-and-drag panning. It's just not a useful enough feature to disrupt the zoom-and-pan muscle memory.
Describe the solution you'd like
The special cursor mode should be activated with an eyedropper toggle like other modules.
Alternatives
Additional context
Holding down the 'a' key while using the mouse disables on-screen controls and allows zooming and panning with the mouse.
I see the issue. Maybe a discussion around general hotkey/modifier conventions in DT could be useful - i.e. I noticed that ALT/Meta is rarely used by DT, and it might be a better modifier to return to zooming.
This is also a problem in lighttable/preview mode. While in zoomable lighttable view, the mousewheel zooms, in culling view ("f") it suddenly moves to the next picture and 'a' also does not work. These kinds of consistency issues should be investigated and solved systematically in my opinion.
The special cursor mode should be activated with an eyedropper toggle like other modules.
In those modules the color picker is an additional tool, not the primary tool. If we implemented your suggestion, then a user would have to turn the module on, then turn on the cursor so that they could use it. So, any user that currently knows how to use tone equalizer would probably be extremely frustrated.
These kinds of consistency issues should be investigated and solved systematically in my opinion.
There are still some hard coded shortcuts that probably should be made configurable. Then users could configure darktable in a way that works best for them.
I like that the ALT/Meta is mostly unused because it gives me a large space to use for my modifiers.
This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.