Details
-
Bug
-
Status: Resolved
-
P4
-
Resolution: Fixed
-
None
-
b15
Description
Whilst working on https://bugs.openjdk.java.net/browse/JDK-8240654
It was noticed that doPrintBand in awt_PrintJob.cpp is only ever called
with a bottom up DIB. Maybe we can get rid of the code path that
handles top-down ? it seems like it was for browser printing since
it supplied a top-down DIB. Although it is still converted to bottom up
for printing because a number of printer drivers did not handle top-down
properly.
JDK's *shared* printing code effectively creates a bottom-up DIB by
setting a transform for the rendering. This meant it did not have to
use up memory by making a reversed copy during printing.
So given that PCs now have vast amounts of RAM compared to when
this code choice was made possibly we could change that shared
code instead and make the top-down case the norm ? Probably not but something to think about.
It was noticed that doPrintBand in awt_PrintJob.cpp is only ever called
with a bottom up DIB. Maybe we can get rid of the code path that
handles top-down ? it seems like it was for browser printing since
it supplied a top-down DIB. Although it is still converted to bottom up
for printing because a number of printer drivers did not handle top-down
properly.
JDK's *shared* printing code effectively creates a bottom-up DIB by
setting a transform for the rendering. This meant it did not have to
use up memory by making a reversed copy during printing.
So given that PCs now have vast amounts of RAM compared to when
this code choice was made possibly we could change that shared
code instead and make the top-down case the norm ? Probably not but something to think about.
