Lister bug with OpenType fonts

[petermad]

[OT]

Time to upgrade?

Well, I have a work Labtop with LCD, and all the monitors at work are LCD. I must say that I am not that impressed, compared to my old Trinitron CRT monitor. So, no, not yet

[dott]

BTW, how can anybody work with Cleartype enabled - I get dizzy looking at all that fuzzyness.

Screenshot1 Screenshot2

ClearType will only work on an LCD. Time to upgrade?

In my SAMUSUNG SyncMaster 794MbPlus Flat CRT

[petermad]

Here is my screenshot - the fuzzyness is obviously worst with the bold font, which I prefer in my file panels:

http://madsenworld.dk/tcmd/cleartype.png

Look for example at the extension "Old" in the fourth file - The "O" and the "l" are completely fused when ClearType is enabled!

[now]

2petermad

Well, the menu font is a lot clearer in my opinion. It’s all a matter of what you prefer, of course. ClearType takes a while to get used to, but I think most people find it a lot better once the initial “blurryness” has faded. Or something like that.

[ghisler(Author)]

Sorry, such fonts aren't supported for the Ansi and Ascii settings.

I am trying to find some reasoning behind this statement.

It was only refering to the non-fixed width font. ANSI and ASCII mode officially support only fixed width fonts, the ones which are offered to choose with the font choose dialog.

Cleartype causes the problem!

I see - I haven't tested that function with Cleartype yet - I hate the blurry look of Cleartype.

The problem here is that I get the right width of the characters, but Cleartype "smears" them to a larger width to create the Cleartype effect...

[now]

You’d think that the text/font measuring functions like GetTextExtentPoint() would work with ClearType, but perhaps they don’t? I mean, the ClearType stuff is all hidden under functions like TextOut() (for example), so the measuring should be correct as well. Or are you using something else?

[ghisler(Author)]

I could fix it now by erasing one more pixel to the left and right of the measured text. Cleartype seems to use these additional pixels to draw the extra "smoothed" pixels.

[roentgen]

2ghisler(Author)
Thanks for taking care

[Alextp]

2ghisler
The "right" solution, IMHO, would be not to erase some pixels to the left/right, but to redraw the whole client area when change occurs...

[Flint]

The "right" solution, IMHO, would be not to erase some pixels to the left/right, but to redraw the whole client area when change occurs...

I'm afraid this would cause lots of flickering...

[Alextp]

2Flint
I don't think so... UV (and also most of editors) repaint the whole client area on every text change - no flickering at all, Windows has internal buffer for this.

[ghisler(Author)]

The "right" solution, IMHO, would be not to erase some pixels to the left/right, but to redraw the whole client area when change occurs...

No, with Cleartype, this would indeed cause a LOT of flickering - you can't just (transparently) overwrite the text, because the halftone parts would become darker and darker then!

I'm not really erasing the pixels, I'm marking them for repaint.

[Alextp]

2ghisler(Author)
Sorry, I don't understand this. But if you tested it, OK, let's erase the pixels.

[petermad]

Fixed in TC 7.02

[ghisler(Author)]

Thanks.