6.18  post-script-dc%

Implements: dc<%>

A post-script-dc% object is a PostScript device context, that can write PostScript files on any platform. See also ps-setup%.

Be sure to use the following methods to start/end drawing:

• start-doc

• start-page

• end-page

• end-doc

See also printer-dc%.

• (new post-script-dc% [(interactive _)] [(parent _)] [(use-paper-bbox _)] [(as-eps _)]) -> post-script-dc% object
     interactive = #t : boolean
     parent = #f : frame% or dialog% object or #f
   use-paper-bbox = #f : boolean
     as-eps = #t : boolean

  If interactive is true, the user is given a dialog for setting printing parameters (see get-ps-setup-from-user); the resulting configuration is installed as the current configuration). If the user chooses to print to a file (the only possibility under Windows and Mac OS X), another dialog is given to select the filename. If the user hits cancel in either of these dialogs, then ok? returns #f.

  If parent is not #f, it is used as the parent window of the configuration dialog.

  If interactive is #f, then the settings returned by current-ps-setup are used. A file dialog is still presented to the user if the get-file method returns #f, and the user may hit cancel in that case so that ok? returns #f.

  If use-paper-bbox is #f, then the PostScript bounding box for the output is determined by drawing commands issued to the object; such a bounding box encloses all parts of the drawing ignoring clipping regions (so the bounding box may be approximate). If use-paper-bbox is not #f, then the bounding box is determined by the current paper size (as specified by current-ps-setup), and the bounding box does not include the margin (also specified by current-ps-setup).

  If as-eps is #f, then the generated PostScript does not include an Encapsulated PostScript (EPS) header, and instead includes a generic PostScript header. Otherwise, the generated PostScript includes a header that identifiers it as EPS.

  See also ps-setup% and current-ps-setup. The settings for a particular post-script-dc% object are fixed to the values in the current configuration when the object is created (after the user has interactively adjusted them when interactive is true).

  
  

All Methods
    clear from dc<%>
    draw-arc from dc<%>
    draw-bitmap from dc<%>
    draw-bitmap-section from dc<%>
    draw-ellipse from dc<%>
    draw-line from dc<%>
    draw-lines from dc<%>
    draw-path from dc<%>
    draw-point from dc<%>
    draw-polygon from dc<%>
    draw-rectangle from dc<%>
    draw-rounded-rectangle from dc<%>
    draw-spline from dc<%>
    draw-text from dc<%>
    end-doc from dc<%>
    end-page from dc<%>
    get-background from dc<%>
    get-brush from dc<%>
    get-char-height from dc<%>
    get-char-width from dc<%>
    get-clipping-region from dc<%>
    get-font from dc<%>
    get-gl-context from dc<%>
    get-origin from dc<%>
    get-pen from dc<%>
    get-scale from dc<%>
    get-size from dc<%>
    get-smoothing from dc<%>
    get-text-background from dc<%>
    get-text-extent from dc<%>
    get-text-foreground from dc<%>
    get-text-mode from dc<%>
    glyph-exists? from dc<%>
    ok? from dc<%>
    set-background from dc<%>
    set-brush from dc<%>
    set-clipping-rect from dc<%>
    set-clipping-region from dc<%>
    set-font from dc<%>
    set-origin from dc<%>
    set-pen from dc<%>
    set-scale from dc<%>
    set-smoothing from dc<%>
    set-text-background from dc<%>
    set-text-foreground from dc<%>
    set-text-mode from dc<%>
    start-doc from dc<%>
    start-page from dc<%>
    try-color from dc<%>