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 349067 - VScale doesn't request enough space for the displayed value
VScale doesn't request enough space for the displayed value
Status: RESOLVED DUPLICATE of bug 79229
Product: gtk+
Classification: Platform
Component: Widget: Other
2.8.x
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2006-07-28 10:49 UTC by Jeremie Knuesel
Modified: 2006-08-05 18:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Attachments
Screenshot for the first problem (not enough space) (3.58 KB, image/png)
2006-07-28 10:50 UTC, Jeremie Knuesel
Details
Screenshot for the second problem (garbled display) (3.93 KB, image/png)
2006-07-28 10:51 UTC, Jeremie Knuesel
Details
Simple test case (657 bytes, text/plain)
2006-07-28 10:52 UTC, Jeremie Knuesel
Details

Description Jeremie Knuesel 2006-07-28 10:49:52 UTC
Please describe the problem:
The width allocated to a vscale widget is not increased when the value displayed above the widget gets too large:

If there is additional space around the widget (eg. HBox spacing or container border-width), text will be drawn in it, but not erased, so that the display gets garbled.



Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Jeremie Knuesel 2006-07-28 10:50:49 UTC
Created attachment 69810 [details]
Screenshot for the first problem (not enough space)
Comment 2 Jeremie Knuesel 2006-07-28 10:51:24 UTC
Created attachment 69811 [details]
Screenshot for the second problem (garbled display)
Comment 3 Jeremie Knuesel 2006-07-28 10:52:27 UTC
Created attachment 69812 [details]
Simple test case
Comment 4 Matthias Clasen 2006-08-05 18:49:04 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 79229 ***