You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Regardless of where the slider actually is, it seems that Ctrl+drag always first executes Ctrl+click, which defaults the control. This can be quite inconvenient, for example if the volume slider was at a low value, and its default value is 0 dB.
We already have defaulting controls on double-click, so Ctrl+click should just do nothing here.
The text was updated successfully, but these errors were encountered:
mkruselj
added
the
UX
Issues related to user experience (UX) - mouse, touch, keyboard, MIDI inputs, etc.
label
May 9, 2020
Here's another tidbit of info: this only happens if you hold Ctrl first, THEN press mouse and drag. If you press mouse to drag and then add Ctrl, it doesn't jump (I guess makes sense, since the drag has already started?).
Regardless of where the slider actually is, it seems that Ctrl+drag always first executes Ctrl+click, which defaults the control. This can be quite inconvenient, for example if the volume slider was at a low value, and its default value is 0 dB.
We already have defaulting controls on double-click, so Ctrl+click should just do nothing here.
The text was updated successfully, but these errors were encountered: