Creating Metafiles for Interchange
The following restrictions apply if the metafile is to be played when the
current drawing-mode parameter is DM_DRAWANDRETAIN or DM_RETAIN, or if the
metafile is to conform to SAA guidelines:
- Before you issue the first drawing instruction to
a graphics presentation space that has been associated with a metafile device
context, you must establish (or default) the following:
You must not specify a graphics field if the metafile
is to conform to SAA guidelines. If a graphics field is specified, you can
play the metafile in DM_RETAIN or DM_DRAWANDRETAIN mode, but the graphics
field must be specified before the first drawing instruction is issued to
the metafile. The effect of the graphics field in the target presentation
space when playing the metafile is controlled by the PMF_LOADTYPE option
of GpiPlayMetaFile.
You
can define logical fonts and identify bit maps to be used as area-fill patterns
at any time. You must not, however, issue GpiDeleteSetId
against these resources after they have been established. Once assigned,
therefore, lcids cannot be reused.
The
size of the logical-color-table data must not exceed 31KB.
You
must not use clipping regions. Therefore, none of the following functions
are supported:
You
must not reassociate the metafile device context.
When
you use a bit map as the source of a GpiWCBitBlt
operation or as an area-fill pattern, it must not be modified.
Only
the following foreground mixes can be used:
- FM_DEFAULT
- FM_OR
- FM_OVERPAINT
- FM_LEAVEALONE
Only
the following background mixes can be used:
- BM_DEFAULT
- BM_OVERPAINT
- BM_LEAVEALONE