Draw-Mode Restrictions

The following restrictions apply if the metafile is to be played when the current drawing mode parameter is DM_DRAW:

• If the DCTL_DISPLAY flag of GpiSetDrawControl is OFF when you are sending graphics to a metafile, the graphics will not be visible when the metafile is played. Their effects on the current position and on current attribute settings are recorded.

• Region functions are not recorded in a metafile. The effects of the following functions, however, are recorded:

  • GpiSetClipRegion
    
  • GpiIntersectClipRectangle
    
  • GpiExcludeClipRectangle
    
  • GpiOffsetClipRegion
    
  • GpiPaintRegion
  When the metafile is played into a presentation space, temporary regions are created. Upon completion of GpiPlayMetaFile, these temporary regions are automatically deleted, and the clipping region that was current before the metafile was played is restored.

In general, escape functions identified by reserved escape codes (that is, escape codes in the range of 0 through 32767) are recorded in a metafile. However, the DevEscape functions DEVESC_QUERYESCSUPPORT (escape code 0) and DEVESC_GETSCALINGFACTOR (escape code 1) are not stored in the metafile.

The effect of GpiErase, including close-segment processing, is recorded in a metafile.

The following functions can produce unexpected effects if the metafile contents are displayed on a different device from the one they were created for:

• GpiBitBlt
  
• GpiSetPel
  
• GpiSetClipRegion
  
• GpiOffsetClipRegion
  
• GpiPaintRegion
  
• GpiIntersectClipRectangle
  
• GpiExcludeClipRectangle
The reason for the unexpected effects is because the pel resolutions of the devices might differ. Raster operations (for example, GpiBitBlt) do not work on plotters.

You can associate the metafile device context with a different presentation space while creating the metafile, but the new presentation space must have the same format as the original.