Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!ucbvax!decwrl!labrea!polya!kaufman
From: kaufman@polya.Stanford.EDU (Marc T. Kaufman)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Text Drawing at speeds greater than 1200baud
Message-ID: <6480@polya.Stanford.EDU>
Date: 31 Jan 89 01:25:10 GMT
References: <1728@helios.ee.lbl.gov> <2534@pegasus.ATT.COM> <25017@apple.Apple.COM>
Reply-To: kaufman@polya.Stanford.EDU (Marc T. Kaufman)
Organization: Stanford University
Lines: 14

In article <25017@apple.Apple.COM> parent@Apple.COM (Sean Parent) writes:

>Also, to quote Inside Mac Vol 1. "The visRgn field is manipulated by the Window
>Manager...The visRgn has no effect on images that aren't displayed on the
>screen." So don't use it in your printing code and keep in mind that it is the
>visable area of a port that is owned by a window.

I have experimental evidence that Quickdraw uses the visRgn  when drawing to
an off-screen GrafPort, if the visRgn is not nil.  There are also some
applications that expect the visRgn to be present, even on a printing
Grafport, so my print drivers set the visRgn == clipRgn == port rect.
What the heck... it can't hurt.

Marc Kaufman (kaufman@polya.stanford.edu)