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 540669 - GtkVolumeButton value changes on opening when located near the edge of the screen.
GtkVolumeButton value changes on opening when located near the edge of the sc...
Status: RESOLVED DUPLICATE of bug 461944
Product: gtk+
Classification: Platform
Component: Widget: Other
2.12.x
Other All
: Normal minor
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2008-06-28 19:36 UTC by Qball Cow
Modified: 2009-02-26 22:01 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Qball Cow 2008-06-28 19:36:15 UTC
GtkVolumeButton value changes on opening when located near the edge of the screen.
F.e. if the volume button is located near the top of the screen, the volume is at say '0', and you click on the volume button, it pops open, moves the window (with the slider) to stay completely on the screen. This however causes the volume slider itself to change. 
People using my program (gmpc) often experience that clicking the button causes the volume to increase, (quoting a user: causing heart-attacks ear pain and perpetual annoyance).


Other information:
I've added a small example video file..
What you see here is the volume at level 0, I click on the button, if I release directly you see it jumps to (here 64%), if I keep my mouse button pressed it does not move UNTIL I move my mouse, or release the button).

http://download.sarine.nl/gtkvolume-bug.ogv
Comment 1 kdekorte 2008-11-12 21:03:21 UTC
I have this same issue with my application, gnome-mplayer, when running video in fullscreen.

gtk2-2.12.12
Comment 2 Sebastien Bacher 2009-02-26 22:01:10 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 461944 ***