The feature is the bomb. It works very well, it even works when I don’t want it to work! I don’t want the feature tampered with, it’s fine, really. The way I see it, we have a conflict of philosophy here of whether the scrolling in the mixconsole is vertical or horizontal.
Because, in the project window, scrolling horizontally is done with a modifier. Shift + mousewheel. Vertical scrolling, or rather, scrolling through the tracks is done by mousewheel only.
Now, I can see how from a tech perspective one would find it elegant and intuitive to say “scrolling through the tracks/channels is done by mousewheel whether in the project or in the mixconsole” and let the user figure out that in the first case it’s in the up/down direction, and in the second case it’s in the left/right direction.
But isn’t it equally intuitive to say “To scroll left/right in any window, use Shift + mousewheel”? In my opinion it is, but then we stumble upon the problem of fine parameter change that is performed by shift+wheel over a value field. Instead of making huge unintended changes, we would only be making very small ones.
It’s not an easy problem to solve. Speaking only for me, my preference would be if Shift+Mousewheel was always reserved for horizontal scrolling, and fine parameter increase/decrease was done by Ctrl+wheel instead of the current Shift+wheel. (Since Ctrl+click also resets the default value). Completely separates the functions of scrolling and editing, guards against accidental tweaks (because Shift+wheeling over a value wouldn’t work), it’s easy to remember since we’re already doing it in the project window and editors. Now, if someone complained that their finger slipped off the wheel, crashed on the left button and reset a value they didn’t want to, well ok, that’s the achilles heel.
Sorry for the long post, I know you are busy.