ReceiveTempSMS
/
Sweden-Number
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

gdi32: GetTextExtentPoint and GetTextExtentExPoint behave differently if there's a \n in the string.

This commit is contained in:
Huw Davies 2006-09-20 14:02:36 +01:00 committed by Alexandre Julliard
parent 7be2957098
commit 8b368b9cee
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
dlls/gdi/tests/font.c
View File

@ -381,8 +381,13 @@ static void test_text_extents(void)
if the extents array is untouched. */
GetTextExtentExPointW(hdc, wt, len, 32767, &fit1, extents, &sz1);
GetTextExtentPointW(hdc, wt, len, &sz2);
ok(sz1.cx == sz2.cx && sz1.cy == sz2.cy,
"results from GetTextExtentExPointW and GetTextExtentPointW differ\n");
ok(sz1.cy == sz2.cy,
"cy from GetTextExtentExPointW (%ld) and GetTextExtentPointW (%ld) differ\n", sz1.cy, sz2.cy);
todo_wine {
/* The \n in the string is apparently handled differently in GetTextExtentPoint and GetTextExtentExPoint */
ok(sz1.cx != sz2.cx,
"cx from GetTextExtentExPointW (%ld) and GetTextExtentPointW (%ld) are the same\n", sz1.cx, sz2.cx);
}
for (i = 1; i < len; ++i)
ok(extents[i-1] <= extents[i],
"GetTextExtentExPointW generated a non-increasing sequence of partial extents (at position %d)\n",