Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!samsung!munnari.oz.au!cluster!jaa
From: jaa@cs.su.oz (James Ashton)
Newsgroups: comp.lang.postscript
Subject: What gsave saves
Message-ID: <742@cluster.cs.su.oz>
Date: 5 Mar 90 01:24:04 GMT
References: <LOKI.90Mar1154035@marvin.moncam.uucp> <18088@rpp386.cactus.org>
Sender: news@cluster.cs.su.oz
Reply-To: jaa@cluster.cs.su.oz (James Ashton)
Distribution: comp
Organization: Basser Dept of Computer Science, University of Sydney, Australia
Lines: 30

In article <18088@rpp386.cactus.org> woody@rpp386.cactus.org (Woodrow Baker) writes:
>On a related topic, does anyone know EXACTLY what is preserved by a gsave.
>grestore pair.  The books say "the current graphics state" and give some
>general things, but so far, I have never seen a comprehensive list of
>EVERYTHING that gets saved.  This would be imensely helpful...

According the (old) manual that I have, "gsave saves only the current
Graphics State, pushing a copy of it onto the Graphics State stack".
It lists the complete set of Graphics State parameters as:

	CTM	Current Transformation matrix
	color
	cp	Current Position
	path	the current path
	clip	the current clipping path
	font	the current font dictionary
	line width
	line cap
	line join
	screen	a collection of PostScript objects that define the
		current halftone screen pattern for grey and colour
	transfer an executable procedure that maps user grey levels
		into device grey levels
	flatness
	miter-limit
	dash
	device	an internal data structure that describes the
		current output device

						James Ashton