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

2006-09-21 Thread Huw Davies
On Thu, Sep 21, 2006 at 01:34:09PM +0900, Dmitry Timoshkov wrote: Huw Davies [EMAIL PROTECTED] wrote: -ok(sz1.cx == sz2.cx sz1.cy == sz2.cy, - results from GetTextExtentExPointW and GetTextExtentPointW differ\n); +ok(sz1.cy == sz2.cy, + cy from GetTextExtentExPointW

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

2006-09-21 Thread Dmitry Timoshkov
Huw Davies [EMAIL PROTECTED] wrote: +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,

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

2006-09-21 Thread Huw Davies
On Thu, Sep 21, 2006 at 06:09:10PM +0900, Dmitry Timoshkov wrote: I accidently left 2 tests in my comment, that may have been misleading. Just to clarify things: an actual test which fails for me is the one in the todo_wine block. Yup, I guessed that's what you meant. I've just sent a patch

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

2006-09-20 Thread Dmitry Timoshkov
Huw Davies [EMAIL PROTECTED] wrote: -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);