-
Bug
-
Resolution: Cannot Reproduce
-
P4
-
None
-
1.2.0
-
None
-
x86
-
windows_nt
To reproduce this problem, run the printing regression test found at:
test/java/awt/PrintJob/PrintComponentTest.
With 2D fonts, the following problems are apparent:
-- On the first page, all lightweight components are printed without their
names.
-- On the second page, names of lightweight components are rendered with lines
radiating from the upper-left corner of the Component. Jim Graham previously
looked at this problem and said "it should go away if we fix any of a
number of bugs related to inefficient use of GDI functions to render curved
paths (see 4152595 and 4152600)." (From the Evaluation for BugId 4151707.)
-- On the second and third pages, the fonts rendered for heavyweight components
are far too small.
With platform fonts, the following problems are apparent:
-- On all three pages, the fonts rendered for heavyweight components are far
too small.
-- On the third page, the fonts rendered for lightweight components are far
too small.
(Also, on the second page, lightweight components do not appear at all. This
is a known AWT problem, not a 2D problem.)
While fonts did not print perfectly for beta4, you could at least work-around
the rendering problems by reenabling platform fonts. Now, doing so introduces
another set of problems. At the very least, Graphics.drawString (i.e.,
lightweight components properly printing their names) should work for FCS.
===================================================
printing problems related to 2D are fixed. There is still a problem with
the positioning of text labels on buttons, which is being referred back to AWT
paul.charlton@eng 1998-09-21
test/java/awt/PrintJob/PrintComponentTest.
With 2D fonts, the following problems are apparent:
-- On the first page, all lightweight components are printed without their
names.
-- On the second page, names of lightweight components are rendered with lines
radiating from the upper-left corner of the Component. Jim Graham previously
looked at this problem and said "it should go away if we fix any of a
number of bugs related to inefficient use of GDI functions to render curved
paths (see 4152595 and 4152600)." (From the Evaluation for BugId 4151707.)
-- On the second and third pages, the fonts rendered for heavyweight components
are far too small.
With platform fonts, the following problems are apparent:
-- On all three pages, the fonts rendered for heavyweight components are far
too small.
-- On the third page, the fonts rendered for lightweight components are far
too small.
(Also, on the second page, lightweight components do not appear at all. This
is a known AWT problem, not a 2D problem.)
While fonts did not print perfectly for beta4, you could at least work-around
the rendering problems by reenabling platform fonts. Now, doing so introduces
another set of problems. At the very least, Graphics.drawString (i.e.,
lightweight components properly printing their names) should work for FCS.
===================================================
printing problems related to 2D are fixed. There is still a problem with
the positioning of text labels on buttons, which is being referred back to AWT
paul.charlton@eng 1998-09-21
- relates to
-
JDK-4204353 printing problems in JDK1.2 using HotJava bean
-
- Resolved
-
-
JDK-4152595 2D API does not use GDI PolyPolyline routine to accelerate rendering on win32
-
- Closed
-
-
JDK-4152600 2D API does not use Bezier rendering routines to accelerate rendering on win32
-
- Closed
-
-
JDK-4151707 Win32 regression: 1.1 printing is broken
-
- Closed
-