Bug 21598 - rendering problem with button text
Summary: rendering problem with button text
Status: WAITING
Alias: None
Product: classpath
Classification: Unclassified
Component: awt (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Thomas Fitzsimmons
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-16 01:21 UTC by Tom Tromey
Modified: 2008-02-17 19:44 UTC (History)
3 users (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed: 2005-05-25 01:57:19

Attachments
test case demonstrating that text is not centered vertically (208 bytes, text/x-java)
2005-09-02 07:16 UTC, Thomas Fitzsimmons 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Tromey 2005-05-16 01:21:10 UTC 
I'm using the applet here:
http://www.chessgames.com/perl/chessgame?gid=1069669
with gcjappletviewer.
(As of this writing I needed a patch to make this work at all,
see the classpath-patches list.)

In this applet, there are some buttons whose text is cut in half.
This happens for all the buttons with text on them.
Comment 1 Tom Tromey 2005-05-22 16:26:31 UTC 
I think the problem here is that the applet calls
setBounds on the buttons in question.  But maybe this is
valid as it explicitly asks for a certain size font?
FWIW the contents of the buttons do look off-center vertically.
Comment 2 Thomas Fitzsimmons 2005-09-02 07:16:24 UTC 
Created attachment 9644 [details]
test case demonstrating that text is not centered vertically
Comment 3 Thomas Fitzsimmons 2005-09-07 04:09:43 UTC 
This is actually a GTK bug; a GtkButton doesn't center its child vertically when
the child's size requisition exceeds its size allocation.  I'm going to write a
GTK test case and submit a bug report and patch.
Comment 4 Thomas Fitzsimmons 2005-09-07 15:48:06 UTC 
I filed a bug against GTK:

http://bugzilla.gnome.org/show_bug.cgi?id=315462
Comment 5 Andrew John Hughes 2008-02-17 19:44:51 UTC 
No feedback on this bug from the Gtk+ developers still...