Newsgroups: comp.windows.x
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!garyo
From: garyo@think.com (Gary Oberbrunner)
Subject: Re: How can I dump a LARGE window to a file?
In-Reply-To: klee@wsl.dec.com's message of 4 Apr 91 01:56:07 GMT
Message-ID: <GARYO.91Apr4111334@prometheus.think.com>
Sender: news@Think.COM
Organization: Thinking Machines Corporation, Cambridge Mass., USA
References: <1991Apr4.012212.7135@am.dsir.govt.nz>
	<1991Apr3.175607@wsl.dec.com>
Date: 4 Apr 91 11:13:34

In article <1991Apr3.175607@wsl.dec.com> klee@wsl.dec.com (Ken Lee) writes:

   In article <1991Apr4.012212.7135@am.dsir.govt.nz>, tony@tui.marcam.dsir.govt.nz (Tony Cooper) writes:
   |> xwd, xsnap, xgrabsc all dump windows to a file but they all suffer from
   |> the problem that they only dump the part of a window that is visible on
   |> the screen.

   Unless you have backing store on, the contents of the not visible parts
   of a window are undefined.

   -- 
   Ken Lee
   DEC Western Software Laboratory, Palo Alto, Calif.
   Internet: klee@wsl.dec.com
   uucp: uunet!decwrl!klee

You could, of course, write a window dump program that put the target
window on top, snarfed as much as was visible, then moved the target window
around (and allowed it to do whatever expose processing it was going to do)
taking snapshots and compositing them together to form an image of what the
whole window would look like if it were all visible.  True, it wouldn't
work in all cases (especially if the display is dynamic in any way), but it
would work for most sensible cases.

				- Gary Oberbrunner
				Thinking Machines Corporation
				245 First St
				Cambridge, MA 02142
				garyo@think.com
