Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!bloom-beacon!dont-send-mail-to-path-lines
From: mouse@lightning.mcrcim.mcgill.EDU (der Mouse)
Newsgroups: comp.windows.x
Subject: Re: How can I dump a LARGE window to a file?
Message-ID: <9104061632.AA02872@lightning.McRCIM.McGill.EDU>
Date: 6 Apr 91 16:32:45 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 20

>>> 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.
> 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)

Except that there's no way for the snapshot program to tell when the
client program is finished doing expose processing.  (Aside from all
the other objections - for example, the window manager may not let you
raise the window all the way to the top; at least some versions tvtwm
won't let you raise it above sticky windows, for example.)

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu