BOOL DrvTextOut(
IN SURFOBJ *pso, | |
IN STROBJ *pstro, | |
IN FONTOBJ *pfo, | |
IN CLIPOBJ *pco, | |
IN RECTL *prclExtra, | |
IN RECTL *prclOpaque, | |
IN BRUSHOBJ *pboFore, | |
IN BRUSHOBJ *pboOpaque, | |
IN POINTL *pptlOrg, | |
IN MIX mix | |
); |
DrvTextOut is the entry point from GDI that calls for the driver to render a set of glyphs at specified positions.
If prclExtra is null then there are no extra rectangles to be rendered.
If the prclExtra is not null then the rectangles are read until a null
rectangle is reached. A null rectangle has both coordinates of both points set
to zero.
The return value is TRUE if the function is successful. Otherwise, it is FALSE, and an error code is logged.
The input parameters to DrvTextOut define two sets of pixels: foreground and opaque. The driver must render the surface so that the result is identical to a process where the opaque pixels are rendered first with the opaque brush, and then the foreground pixels are rendered with the foreground brush. Each of these operations is limited by clipping.
The foreground set of pixels is defined to be the union of the pixels of the glyphs with the pixels of the extra rectangles at prclExtra. These extra rectangles are used to simulate strike-through or underlines. The opaque pixels are defined by the opaque rectangle at prclOpaque.
The foreground and opaque pixels are regarded as a screen through which color is brushed onto the surface. The glyphs of the font do not have color in themselves.
The input parameters to DrvTextOut define the set of glyph pixels, the set of extra rectangles, the opaque rectangle, and the clip region. It is the driver’s responsibility to calculate and then render the set of foreground and opaque pixels.
GDI guarantees that DrvTextOut and DrvDestroyFont never overlap; consequently, the driver can rely on cached information while processing a DrvTextOut call.
The mix mode defines how the incoming pattern should be mixed with the data already on the device surface. The MIX data type consists of two ROP2 values packed into a single ULONG. The low-order byte defines the foreground raster operation; the next byte defines the background raster operation. For more information about raster operation codes, see the Win32 SDK.
This is a required function.