Path: utzoo!attcan!uunet!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!sdd.hp.com!ucsd!ucbvax!bloom-beacon!eru!luth!sunic!tut!funic!csc.fi!hnevanlinna
From: hnevanlinna@csc.fi
Newsgroups: comp.sys.mac.programmer
Subject: Why SetStdProcs, why not GetQDProcs or something ?
Message-ID: <1990Jul8.123027.1@csc.fi>
Date: 8 Jul 90 12:30:27 GMT
Sender: usenet@funic.funet.fi
Organization: Finnish Academic and Research Network Project - FUNET
Lines: 34


	I have made a small MacApp-program to create PICT-files.
	PICTs are created at opening a new document, spoed to file
	and then displayed on view either by spooling or if wanted by
	offscreen buffer.  I also use the method of setting laser to
	300 bpi resolution like in FracApp300, so I get maximum resolution
	on any device.

	OK, that's for backround.  I used to PICT-spooling examples in IM V
	to spool the picture to the file ( with a little more error handling ).
	All worked well, when I spooled the PICT to the VIEW by it's draw
	method.  But I didn't get anything on printer.  I did some 
	modifications on my code and the printing work by NOT using the
	SetStdProcs, but directly saving and changing the getPicProc-field
	in grafprocs.  I didn't test, but I thougt printer might have
	the grafprocs modified a little.

	Anyway it works now.  What I like to now is there any reason
	to use SetStdProcs, when I might be drawing in the port, wh
	for some reasons allready have it's lowlevel procs modified.
	Better routine would be GetQDProcs, which would g the CURRENT
	drawing procs. ( I know that in such situation there might be some
	compatibility problems, but it's better? than having the procs
	zapped to standard routines )

	Or have I misunderstood the whole concept ?


				Jouni Ryn|
				Finnish Meteorological Institute
				Departement of Geophysics

	'I have nothing to do with bad weather'