|
|
|
|
|
Thanks. I played a bit with the patch and noticed that, since TextOut ignores TextStyle, all TextStyle-related assignments can be removed. Store/RestoreCanvasProperties should not be dropped: In the demo html text change the line after "<h2>Description</h2>" to "<p style="background-color:red;"><var>Name</var> is the name of the component..." Run. Select part of the red text. Scroll down --> Text after the selection becomes white when the RestoreWordStyle box is not selected in your demo. Can you point me to a location in the demo output to see why "P.X := P.X + 1" is needed for the space character? |
|
|
> Can you point me to a location in the demo output to see why "P.X := P.X + 1" is needed for the space character? Note word "Name" after "Description" header. Last pixels got cut off by space character. |
|
|
There is a problem with selected text: Check "UseTextOut" and drag the mouse over some text. While most of the text has the background in the corresponding color there are some lines left after some words. In the attached screenshot see the vertical lines before "name" and before "character". The lines disappear when a repaint is enforced, for example by scrolling or pressing the "Refresh" button. 38318.png (6,993 bytes) |
|
|
Question: what about Right-to-Left text? The TIpHtmlPanel currently doesn't support it (though at least the dir attribute is parsed already), but using TextStyle would be one possibility to achive it and as wp said, TextOut ignores TextStyle. |
|
|
Good point! I'm in doubt about this issue, too. Factor 3 sounds dramatic (it's only a factor 2 for me, still...), but playing with serbod's demo I don't notice any difference at user level. Are we sure that there is an attempt to paint any text outside the visible window? If out-of-view text is clipped I think we can ignore this optimization in favour of more flexibility for other issues. |
- Anonymous
