Steema Issues Database

Note: This database is for bugs and wishes only. For technical support help, if you are a customer please visit our online forums;
otherwise you can use StackOverflow.
Before using this bug-tracker we recommend a look at this document, Steema Bug Fixing Policy.



Bug 208

Summary: [TV52015253] In TeCanvas the following line appears to me to contain a bad choice ...
Product: VCL TeeChart Reporter: narcís calvet <narcis>
Component: CanvasAssignee: Steema Issue Manager <issuemanager>
Status: RESOLVED WONTFIX    
Severity: major CC: david
Priority: Normal    
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Chart Series: --- Delphi / C++ Builder RAD IDE Version:

Description narcís calvet 2013-11-20 10:03:36 EST 
In TeCanvas the following line appears to me to contain a bad choice of default value:

TeeFontAntiAlias:Byte=ANTIALIASED_QUALITY

For fonts that rely on clear type smoothing (e.g. Segoe UI, the MS C font family introduced with Office 2007) the resulting text looks dreadful. A much better choice would be DEFAULT_QUALITY and this is in fact what the plain vanilla Delphi TFont code uses when it calls CreateFontIndirect in TFont.GetHandle.

For what it's worth, the MSDN documentation of LOGFONT.lfQuality is terrible, but my understanding is that DEFAULT_QUALITY results in font smoothing based on the system settings. It makes sense to me for TeeChart to use the system settings as its default.

Well, it results in worse rendering, at least on my system (vanilla Windows 7). [created:2010-10-28T15:01:08.000+01:00 reported by:narcis@steema.com reported in version:2010.01.11004 (TeeChart VCL)]
Comment 1 david berneda 2023-03-17 02:05:49 EDT 
GDI+ solves typographic quality

This blog post provides complete info about text output differences between gdi and gdi+:

https://theartofdev.com/2013/08/12/using-native-gdi-for-text-rendering-in-c/