Enabling Antialiased Fonts

You can enable antialiased fonts as the default if your display driver supports such fonts. Windows CE uses antialiased fonts by default if you add the HKEY_LOCAL_MACHINE\System\GDI\Fontsmoothing registry key. If this key ispresent, and you do not want your application to get an antialiased font, you must specify NONANTIALIASED_QUALITY in the lfQuality member of the LOGFONT structure for your application. If this key is notpresent, and you want your application to retrieve an antialiased font, you must specify ANTIALIASED_QUALITY in the lfQuality member of the LOGFONT structure for your application.

Add the ForceGRAY16 value to the HKEY_LOCAL_MACHINE\System\GDI registry key to allow or disallow the TrueType font renderer to use 4-bit antialiasing for font sizes that do not support 4-bit antialiasing. Setting this value to 1 will enable the antialiasing in the TrueType font renderer, and setting it to 0 will disable the antialiasing in the TrueType font renderer.

Add the ExpensiveAntialias value to the HKEY_LOCAL_MACHINE\System\GDI registry key to use an alternative antialiasing algorithm in the GPE Emul library. Setting this value to 1 will enable the use of an antialiasing algorithm, and setting it to zero (0) will disable the use of an alternate antialiasing algorithm. Any display driver using the Emul library can thus take advantage of two possible antialiasing algorithms.

The following code example shows the ForceGRAY16 and ExpensiveAntialias registry values set to 1.

[HKEY_LOCAL_MACHINE\System\GDI]
    "ForceGRAY16"=dword:1
    "ExpensiveAntialias"=dword:1

See Also

Customizing Fonts | Fonts Implementation Considerations | Fonts

Last updated on Wednesday, April 13, 2005

© 2005 Microsoft Corporation. All rights reserved.