Make Mouse Wheel in Console Window Consistent with Tracks Pane

[Tim Elmore]

Background: CbB version 2020.05 made the mouse wheel less prone to accidentally adjusting control settings if the user pauses during a vertical scroll with the mouse wheel. If the user pauses briefly during scrolling, there is a delay before the next mouse movement is treated as a new operation. Version 2020.05 increased this delay from 0.5 second to one second.

Problem: This helps, but I still inadvertently change a control value if I start scrolling while I happen to be hovering over a control. Even though I am very careful about this, I sometimes accidentally bump the sensitive mouse wheel as I take hold of the mouse to scroll the pane. The constant necessity for being really careful is a distraction.

Solution: The Tracks Pane already has a really nice way to handle the mouse wheel. To change a Tracks Pane control setting, you left-click the control first. This selects the control, indicated by putting thin brackets around the control (see attached figure). The mouse wheel can then be used to change the setting. If a control is not selected, there is no danger of an inadvertent change. A control can be deselected by clicking a blank area of the Tracks Pane. This completely prevents unintended changes in settings when moving the mouse and scrolling around the Tracks Pane.

Oddly, although the Console Pane allows the user to select a control by left-clicking it, this seems to have no effect on the behavior of the control, unlike in the Tracks Pane. A Console Pane control can be changed using the mouse wheel even though the control is not selected. In the attached figure, I had inadvertently moved the Pan control in the Console Pane from the centered position.

If the Console Pane were to treat control selection the same as the Tracks Panel (left-click before allowing mouse wheel to change a setting), it would completely eliminate inadvertent control changes in the Console Pane when using the mouse wheel.

[Jim Fogle]

Excellent suggestion.  I always try to agree with suggestions that enable CbB to operate consistently between views.

[marcL]

For me it is the contrary, because most of the plugins today allow to use the mouse wheel just by positioning the mouse over a control. Thus if it is required to click the control first to use the mouse wheel, I often forget the click and that causes sometimes that the previous clicked control is changed. The bad thing is also that this control is not in my current focus, i.e. in the worst case I even don't know what control I have changed, but in all cases I do not know the old value. That's why I prefer that the mouse position is relevant to change a value and not a click on the control!

[Tim Elmore]

The way the Tracks Pane works right now, a left-click is required, and the mouse cursor must be over the control to change it. In the Tracks Pane, if you forget to click the control you want to change, and you hover the mouse over it and move the mouse wheel, nothing will happen. But at least it doesn't change the wrong control.

Some people will prefer to just move the mouse over the control and not have to left-click it before using the mouse wheel. Maybe the best thing to do is make this the default for both the Tracks Pane and Console Pane, and add a settable option to require a left-click first. The Tracks Pane and Console Pane would then be consistent. Right now, a left-click is required in the Tracks Pane, but not in the Console Pane.

[user 905133]

1 hour ago, Tim E. said:

Some people will prefer to just move the mouse over the control and not have to left-click it before using the mouse wheel. Maybe the best thing to do is make this the default for both the Tracks Pane and Console Pane, and add a settable option to require a left-click first. The Tracks Pane and Console Pane would then be consistent. Right now, a left-click is required in the Tracks Pane, but not in the Console Pane.

This seems to be consistent with Cakewalk's customization flexibility.  I have been wanting the scroll wheel to work in the Notes Browser when in edit mode (it works in read mode), but it makes sense to me to have each view/subview have its own settable assortment of mouse wheel options. 

Edited October 4, 2020 by User 905133
grammatical corrections

[sjoens]

I agree.

Slightly OT but what I don't get, in 2020.04 with Auto Track Zoom on, if you stretch all tracks to see all controls and then click on track 2 to focus it, it diminishes to default height. Now I have to resize it  *again* to work in it. Makes no sense to me.

Edited October 18, 2020 by sjoens

[reginaldStjohn]

22 hours ago, sjoens said:

I agree.

Slightly OT but what I don't get, in 2020.04 with Auto Track Zoom on, if you stretch all tracks to see all controls and then click on track 2 to focus it, it diminishes to default height. Now I have to resize it  *again* to work in it. Makes no sense to me.

That is because there are two states, the selected track size and un-selected size. If you adjust an unselected track all the tracks, except the selected one will resize and become the unselected size. Then when you select a different track it will go to the selected state which you did not modify in the previous action and the previously selected track will go to the new unselected size. 

[sjoens]

Thanks for the explanation.