Important Notice

The pages on this site contain documentation for very old MS-DOS software, purely for historical purposes. If you're looking for up-to-date documentation, particularly for programming, you should not rely on the information found here, as it will be woefully out of date.

                                                     ◄Up► ◄Next► ◄Previous►
────────────────────────────────────────────────────────────────────────────
 
#define SETKERNTRACK 770 
short Control(lpDevice, SETKERNTRACK, lpInData, lpOutData)
LPPDEVICE lpDevice;
LPINT lpInData;
LPINT lpOutData;
 
The SETKERNTRACK escape specifies which kerning track a driver that supports
automatic-track kerning should use. A kerning track of zero disables
automatic-track kerning. When this escape is enabled, the driver
automatically kerns all characters according to the specified track. The
driver reflects this kerning both on the printer and in calls to the
GetTextExtent (GDI.91) function.
 
Parameter  Description
────────────────────────────────────────────────────────────────────────────
 
lpDevice   Points to a PDEVICE structure specifying the destination device.
 
lpInData   Points to a 16-bit variable that specifies the kerning track to
           use. A value of zero disables this feature. The etmKernTracks
           member in the EXTTEXTMETRIC structure for the driver specifies
           the maximum permitted value. Each permitted value corresponds to
           a position in the track-kerning table (using one as the first
           item in the table).
 
lpOutData  Points to a 16-bit variable that receives the previous kerning
           track.
 
Return Value
 
The return value is 1 if the escape is successful. Otherwise, it is 0 if it
is not, or if the escape is not implemented.
 
Comments
 
The default state is zero, which means that automatic-track kerning is
disabled.
 
A driver does not have to support this escape just because it supplies the
track-kerning table to the application using the GETTRACKKERNTABLE escape.
In the case where GETTRACKKERNTABLE is supported but SETKERNTRACK is not, it
is the application's responsibility to properly space the characters on the
output device.
 
See Also
 
GETEXTENDEDTEXTMETRICS, GETTRACKKERNTABLE, EXTTEXTMETRIC, PDEVICE
 
 
                                      ♦