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 - [TV52015253] In TeCanvas the following line appears to me to contain a bad choice ...
Summary: [TV52015253] In TeCanvas the following line appears to me to contain a bad ch...
Status: RESOLVED WONTFIX
Alias: None
Product: VCL TeeChart
Classification: Unclassified
Component: Canvas (show other bugs)
Version: unspecified
Hardware: All All
: Normal major
Target Milestone: ---
Assignee: Steema Issue Manager
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-28 16:01 EDT by narcís calvet
Modified: 2023-03-17 02:05 EDT (History)
1 user (show)

See Also:
Chart Series: ---
Delphi / C++ Builder RAD IDE Version:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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/