... | @@ -189,7 +189,7 @@ ttf-Courier-rrncns-*-16-UTF-8 |
... | @@ -189,7 +189,7 @@ ttf-Courier-rrncns-*-16-UTF-8 |
|
## API Enhancements
|
|
## API Enhancements
|
|
|
|
|
|
For a new app, you should use the new function `CreateLogFontEx` to
|
|
For a new app, you should use the new function `CreateLogFontEx` to
|
|
create a LOGFONT, and specify the weight and rendering method of the glyph:
|
|
create a logfont, and specify the weight and rendering method of the glyph:
|
|
|
|
|
|
```
|
|
```
|
|
m_btnFont = CreateLogFontEx ("ttf", "helvetica", "UTF-8",
|
|
m_btnFont = CreateLogFontEx ("ttf", "helvetica", "UTF-8",
|
... | @@ -202,11 +202,11 @@ m_btnFont = CreateLogFontEx ("ttf", "helvetica", "UTF-8", |
... | @@ -202,11 +202,11 @@ m_btnFont = CreateLogFontEx ("ttf", "helvetica", "UTF-8", |
|
```
|
|
```
|
|
|
|
|
|
For the backward compatibility, you can still use `CreateLogFont` to create a new
|
|
For the backward compatibility, you can still use `CreateLogFont` to create a new
|
|
LOGFONT. However, `FS_WEIGHT_BOOK` will be treated `FS_WEIGHT_REGULAR` and
|
|
logfont. However, `FS_WEIGHT_BOOK` will be treated `FS_WEIGHT_REGULAR` and
|
|
`FS_RENDER_GREY`, while `FS_WEIGHT_SUBPIXEL` will be treated
|
|
`FS_RENDER_GREY`, while `FS_WEIGHT_SUBPIXEL` will be treated
|
|
`FS_WEIGHT_REGULAR` and `FS_RENDER_SUBPIXEL`.
|
|
`FS_WEIGHT_REGULAR` and `FS_RENDER_SUBPIXEL`.
|
|
|
|
|
|
You can still use `CreateLogFontByName` to create a new LOGFONT. But you should
|
|
You can still use `CreateLogFontByName` to create a new logfont. But you should
|
|
make sure to define the new logfont name in new format.
|
|
make sure to define the new logfont name in new format.
|
|
|
|
|
|
We also introduced the following new functions in version 4.0.0:
|
|
We also introduced the following new functions in version 4.0.0:
|
... | | ... | |