DEVMODE

typedef struct _DEVMODE {
     char  dmDeviceName[CCHDEVICENAME];
    UINT  dmSpecVersion;
    UINT  dmDriverVersion;
    UINT  dmSize;
    UNIT  dmDriverExtra;
    DWORD dmFields;
    int   dmOrientation;
    int   dmPaperSize;
    int   dmPaperLength;
    int   dmPaperWidth;
    int   dmScale;
    int   dmCopies;
    int   dmDefaultSource;
    int   dmPrintQuality;
    int   dmColor;
    int   dmDuplex;
    int   dmYResolution;
    int   dmTTOption;
    int   dmCollate;
    TCHAR dmFormName[CCHFORMNAME];
    WORD  dmLogPixels;
    DWORD dmBitsPerPel;
    DWORD dmPelsWidth;
    DWORD dmPelsHeight;
    DWORD dmDisplayFlags;
    DWORD dmDisplayFrequency;
    DWORD dmICMMethod;
    DWORD dmICMIntent;
    DWORD dmMediaType;
    DWORD dmDitherType;
    DWORD dmReserved1;
    DWORD dmReserved2;
} DEVMODE;
 

Structure that contains information about the device initialization and environment of a printer. An application passes this structure to DeviceCapabilities and ExtDeviceMode functions exported by the driver. The DEVMODE structure is defined in PRINT.H.

DEVMODE members which are new to Windows 95 are defined below.

Using DMCOLLATE_FALSE provides faster, more efficient output, since the data is sent to a page printer just once, no matter how many copies are required, and the printer is instructed to simply print the page again.

The printer driver must provide a user interface for setting the dmICMMethod member of the DEVMODE structure. Most printer drivers support only the DMICMMETHOD_SYSTEM or DMICMMETHOD_NONE methods, although drivers for PostScript printers support all values.

The dmICMIntent member of the DEVMODE structure is used primarily by applications that do not support ICM. ICM-capable functions can establish color-matching algorithms by using the ICM functions.

A driver can define values for this member that are greater than the value DMMEDIA_USER.

Printer drivers that support the new members in the DEVMODE structure must set DEVMODE.dmSpecVersion to 0x0400. If a driver sets DEVMODE.dmSpecVersion to this value, the driver must also meet the following requirements:

• The driver must always return 0x0400 to a DeviceCapabilities function call that uses a DC_VERSION argument.
• The driver must use the new DEVMODE structure definition, even if it does not use any of the new members (it should initialize them to zero).
• The driver must use DrvSetPrinterData to store printer driver settings and use DrvGetPrinterData to retrieve them.
• The driver must be able to handle friendly user-defined printer names, which can be any string up to 32 characters in length (including the terminating NULL character). When an application passes the driver a friendly printer name, the driver must query the registry to determine what the corresponding printer model name is. The driver can use the DrvGetPrinterData function to do this.
• If the DEVMODE data retrieved from the registry is incorrect, the driver must build a default DEVMODE and merge as many member values as possible, and then update the registry. Win32 applications can use the DEVMODE structure, so the driver must update DEVMODE.dmDeviceName with the current friendly printer name.
• Private DEVMODE data must contain the printer model name or some way of determining the current printer model name.
• The driver does not have to contain code that writes settings to INI files since these settings are now maintained on the registry. The driver may have to contain code that reads INI files.

In addition to the requirements listed above, there are two other more detailed requirements which are described below:

• The driver must handle brushes differently than in Windows 3.x.
• The driver must organize the private members of the DEVMODE structure into two groups: printer-sticky members and document-sticky members.