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 342276 - improper widget packing in volume-control
improper widget packing in volume-control
Status: RESOLVED WONTFIX
Product: gnome-media
Classification: Deprecated
Component: gnome-volume-control
2.14.x
Other Linux
: Normal trivial
: ---
Assigned To: gnome media maintainers
gnome media maintainers
Depends on:
Blocks:
 
 
Reported: 2006-05-18 18:08 UTC by Daniel Holbach
Modified: 2006-05-29 14:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Daniel Holbach 2006-05-18 18:08:47 UTC
Forwarded from: https://launchpad.net/distros/ubuntu/+source/gnome-media/+bug/45446

Switching across the playback and capture tags causes an annoying "drift" of the sliders, that must be because of the sliders in the "capture" tag having two icons at the bottom.

http://librarian.launchpad.net/2734860/Schermata-Regolazione%20volume%3A%20NVidia%20nForce2%20%28Alsa%20mixer%29.png
http://librarian.launchpad.net/2734861/Schermata-Regolazione%20volume%3A%20NVidia%20nForce2%20%28Alsa%20mixer%29-1.png

(through an image viewer (eog will do) "browse through" these two screenshots, the misalignment is evident"
Comment 1 Ronald Bultje 2006-05-29 14:26:00 UTC
It's because the text (label) has a different size, causing more space to be allocated for some than for other slider-boxes. If any, that would be a GtkBox packing bug. I can see how this is mildly annoying, but this is useful if you have multiple slides, where one is small and one is large (text-size-wise): you don't want both to have the same size, because then you're wasting valuable real estate (screen space). Therefore, they're set to no-same-size, and the result is this slight "drift". I don't consider that improper at all.

Therefore, I don't consider this a bug, I'm affraid. It's intended behaviour.