Re: gdi32: Printer drivers don't use the character extra spacing if lpdx is supplied.
Huw Davies <huw(a)codeweavers.com> writes:
Ideally this would be done in wineps.drv, but by that point the conversion to device units would cause rounding errors.
What about GetTextExtent functions? Do they need this too? Some test cases would be nice. -- Alexandre Julliard julliard(a)winehq.org
On Tue, Mar 26, 2013 at 04:30:14PM +0100, Alexandre Julliard wrote:
Huw Davies <huw(a)codeweavers.com> writes:
Ideally this would be done in wineps.drv, but by that point the conversion to device units would cause rounding errors.
What about GetTextExtent functions? Do they need this too? Some test cases would be nice.
Note this only applies when lpDx != NULL, when it's NULL then char_extra is still applied. So, yes the current GetTextExtent behaviour is correct. Huw.
Huw Davies <huw(a)codeweavers.com> writes:
On Tue, Mar 26, 2013 at 04:30:14PM +0100, Alexandre Julliard wrote:
Huw Davies <huw(a)codeweavers.com> writes:
Ideally this would be done in wineps.drv, but by that point the conversion to device units would cause rounding errors.
What about GetTextExtent functions? Do they need this too? Some test cases would be nice.
Note this only applies when lpDx != NULL, when it's NULL then char_extra is still applied. So, yes the current GetTextExtent behaviour is correct.
Ah OK, I guess that makes it a PITA to test... -- Alexandre Julliard julliard(a)winehq.org
participants (2)
-
Alexandre Julliard -
Huw Davies