Bug 444252 - RFE: accept mouse scroll wheel within each volume element
RFE: accept mouse scroll wheel within each volume element
Product: Fedora
Classification: Fedora
Component: pavucontrol (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Lennart Poettering
Fedora Extras Quality Assurance
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2008-04-25 22:07 EDT by David Timms
Modified: 2009-02-13 19:37 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-02-13 19:37:58 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
suggested hot zones (29.63 KB, image/png)
2008-04-25 22:37 EDT, David Timms
no flags Details

  None (edit)
Description David Timms 2008-04-25 22:07:20 EDT
Description of problem:
Positioning the mouse on those skinny volume bars could be improved by not
requiring it. Make it easier to adjust these levels by accepting the mouse
scroll wheel up/down event within each volume element.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. pavucontrol
2. put mouse for example between the left and right volume bars, and scroll the
mouse wheel up/down
Actual results:

Expected results:
adjust the volume pair.
If unlocked, adjust each by same dB.
Comment 1 David Timms 2008-04-25 22:37:23 EDT
Created attachment 303844 [details]
suggested hot zones

if linked {locked}: orange and yellow accepts scroll events
if unlinked : orange accepts scroll events for tracked level change.
Comment 2 Matthias Clasen 2009-02-13 19:37:58 EST
I don't think keeping this feature request open here will do much good.
We are not going to work on pavucontrol features; we've just rewritten gnome-volume-control to control pulseaudio...

If you still care about this, please file it upstream at http://www.pulseaudio.org/

Note You need to log in before you can comment on or make changes to this bug.