After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 510572 - Make tooltip update immediately when volume is changed by mousescroll
Make tooltip update immediately when volume is changed by mousescroll
Status: RESOLVED FIXED
Product: gnome-applets
Classification: Other
Component: mixer
2.20.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
: 467128 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-01-19 10:04 UTC by Nguyen Thai Ngoc Duy
Modified: 2009-02-02 08:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20

Attachments
mixer-tooltip.patch (355 bytes, patch)
2008-01-19 10:06 UTC, Nguyen Thai Ngoc Duy 		none Details | Review

Description Nguyen Thai Ngoc Duy 2008-01-19 10:04:26 UTC 
Earlier versions (I don't remember exactly) I could mouse-scroll on mixer applet and see the volume percentage change in tooltip.

With gnome-applets 2.20.0, the tooltip lags. It updates percentage value a scroll later. (if it's at 25%, one scroll up and one scroll down, you get 29% in the tooltip while the real value is 25%, no mouse move).
Comment 1 Nguyen Thai Ngoc Duy 2008-01-19 10:06:02 UTC 
Created attachment 103189 [details] [review]
mixer-tooltip.patch

This works for me.
Comment 2 Cosimo Cecchi 2008-03-03 11:17:28 UTC 
I tested this and it works fine for me. Can we have this in for 2.22?
Comment 3 Teppo Turtiainen 2008-04-09 17:47:22 UTC 
*** Bug 467128 has been marked as a duplicate of this bug. ***
Comment 4 Leon 2008-04-12 14:39:03 UTC 
This was originally fixed in bug 320123 - I'm not a coder but maybe the comparison is helpful? Anyway, can I add my !vote for inclusion in 2.22?
Comment 5 Callum McKenzie 2009-02-02 08:55:46 UTC 
This appears to be fixed in 2.25. There was some rearrangement of the updates in the 2.23 time-frame, so that may have been what fixed it.