Microsoft KB Archive/111651: Difference between revisions

From BetaArchive Wiki
m (1 revision imported: importing part 1)
m (Text replacement - """ to """)
 
Line 26: Line 26:
Calling '''GetGlyphOutline()''' for a bitmap and passing a large X or Y scaling factor in the transformation matrix causes the return value to not properly track the bitmap size.<br />
Calling '''GetGlyphOutline()''' for a bitmap and passing a large X or Y scaling factor in the transformation matrix causes the return value to not properly track the bitmap size.<br />
<br />
<br />
For example, Times New Roman Regular 72 point &quot;1&quot;, with a scaling factor of 4.0 in eM11 of the transformation matrix, returns a black box of 100,64. This requires a bitmap of at least 800 bytes but '''GetGlyphOutline()''' only returns 256. The native buffer is returned with no problems.
For example, Times New Roman Regular 72 point "1", with a scaling factor of 4.0 in eM11 of the transformation matrix, returns a black box of 100,64. This requires a bitmap of at least 800 bytes but '''GetGlyphOutline()''' only returns 256. The native buffer is returned with no problems.


<br />
<br />
Line 33: Line 33:
== CAUSE ==
== CAUSE ==


A 12-point font on a VGA is marked to use the rasterizer's scan converter. However, if the scaling indicated in the transform exceeds the outline threshold, GDI's &quot;external&quot; scan converter should be used. Unfortunately, that condition is not detected.<br />
A 12-point font on a VGA is marked to use the rasterizer's scan converter. However, if the scaling indicated in the transform exceeds the outline threshold, GDI's "external" scan converter should be used. Unfortunately, that condition is not detected.<br />
<br />
<br />
'''NOTE''': This problem occurs only with bitmaps; outlines are fine with all transformation matrices.
'''NOTE''': This problem occurs only with bitmaps; outlines are fine with all transformation matrices.

Latest revision as of 11:26, 20 July 2020

BUG: GetGlyphOutline() with GGO_BITMAP Fails with Large Scale

Q111651

3.10 WINDOWS kbprg kbbuglist



The information in this article applies to:


  • Microsoft Windows Software Development Kit (SDK) 3.1





SYMPTOMS

Calling GetGlyphOutline() for a bitmap and passing a large X or Y scaling factor in the transformation matrix causes the return value to not properly track the bitmap size.

For example, Times New Roman Regular 72 point "1", with a scaling factor of 4.0 in eM11 of the transformation matrix, returns a black box of 100,64. This requires a bitmap of at least 800 bytes but GetGlyphOutline() only returns 256. The native buffer is returned with no problems.



CAUSE

A 12-point font on a VGA is marked to use the rasterizer's scan converter. However, if the scaling indicated in the transform exceeds the outline threshold, GDI's "external" scan converter should be used. Unfortunately, that condition is not detected.

NOTE: This problem occurs only with bitmaps; outlines are fine with all transformation matrices.



STATUS

Microsoft has confirmed this to be a bug in Windows version 3.1.

Additional query words: buglist3.10 3.10 truetype font

Keywords : kbSDKWin16
Issue type : kbbug
Technology : kbAudDeveloper kbWin3xSearch kbSDKSearch kbWinSDKSearch kbWinSDK310


Last Reviewed: June 24, 1999
© 2001 Microsoft Corporation. All rights reserved. Terms of Use.