JDK-4414577 : TextLayout getVisualBounds slow for Latin-1 text
Type:Bug
Component:client-libs
Sub-Component:2d
Affected Version:1.4.0
Priority:P4
Status:Resolved
Resolution:Fixed
OS:generic
CPU:generic
Submitted:2001-02-13
Updated:2001-07-10
Resolved:2001-07-10
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed. Resolved: Release in which this issue/RFE has been resolved. Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
Currently the only API to get the visual bounds of text with layout is on TextLayout, but this is slower it seems it could be for latin-1 text. Please look into speeding this up.
Comments
CONVERTED DATA
BugTraq+ Release Management Values
COMMIT TO FIX:
merlin-beta2
FIXED IN:
merlin-beta2
INTEGRATED IN:
merlin-beta2
14-06-2004
SUGGESTED FIX
Since the problems are for Latin-1, and we don't do layout for Latin-1, and the metrics desired are full line (logical and visual bounds) it seems possible to defer full initialization of the TextLayout (at the cost of hanging on to the text) and use a Font-and-FRC-specific cache of char/glyph metric information. This is similar to how the FontMetrics object works. Holding on to the text would also let us render the text without instantiating a glyphvector (currently marginally faster). We could only do full layout when we need per-character information such as is needed for highlighting or caret placement.
11-06-2004
PUBLIC COMMENTS
Currently the only API to get the visual bounds of text with layout is on TextLayout, but this is slower it seems it could be for latin-1 text.
10-06-2004
EVALUATION
Implement the suggested fix.
doug.felt@eng 2001-07-06