Jump to content

PDRREF:Graphics Engine Hardcopy Drivers

From EDM2
Revision as of 17:49, 19 November 2019 by Martini (talk | contribs) (Created page with "For the Presentation Manager interface, hardcopy devices, such as printers and plotters, are queued devices. When an application writes to one of these devices, the presentati...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

For the Presentation Manager interface, hardcopy devices, such as printers and plotters, are queued devices. When an application writes to one of these devices, the presentation driver creates a spool file and writes the data to that file. The data is printed when it is complete and the required device is free.

Two instances of a device context are required to support queued data. The first instance is opened as an OD_QUEUED device by the application. This DC buffers the data, does any processing that is required, and then writes the data to a spool file. The second instance is opened as an OD_DIRECT device by the queue processor. This DC receives data from the spool file, does any processing that is required, and by using the Prtxxx interface, sends the data to the final output destination, such as port, device, or UNC name.

When a device context is opened, the data type given (PM_Q_STD or PM_Q_RAW) is applicable only for the OD_QUEUED device context type.

Exported Entry Points

InnerGre Entries

GRE Macro Expansion

InnerGre Macros

File System Expansion

Spooler Support for POM_Q_STD Data Type

Spooler Componets

Output Directly to Device

PM_Q_STD

Normal Sequence of Events;

End Sequence of Events

PM_Q_RAW

Normal Sequence of Events

End Sequence of Events

Querying and Setting Configuration Data

Spooler Support Functions