Path: utzoo!attcan!uunet!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!swrinde!ucsd!ucbvax!UMIX.CC.UMICH.EDU!krowitz%richter
From: krowitz%richter@UMIX.CC.UMICH.EDU (David Krowitz)
Newsgroups: comp.sys.apollo
Subject: Re:  PostScript File from gmr2D
Message-ID: <9005311315.AA03360@richter.mit.edu>
Date: 31 May 90 13:15:04 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 23

If my memory serves me correctly, I recall that the GMR-2D manual
mentions that the "within GPR" mode of GMR disables a fair amount
of the auto scaling, translation, etc. functions of GMR. I think
this would apply to the GMR_$PRINT... calls, too. 

We use the GM_$PRINT_FILE call to produce GMF bitmap files and OUT1
vector-dump files (for later translation to HPGL) in a wide range of
home-built graphics utilities. In general, we have had a *LOT* of
problems with it -- incorrect instance/transform operations, missing
text strings, internal arithmetic overflows, etc. The situation has
not gotten better with GMR-2D version 2.0 - 2.2 (the SR10 versions of
2D GMR). If anything, they have become worse. I have just received
version 2.3 of 2D GMR, which I will install and test in a day or two
to see if it fixes any of the bugs which Apollo introduced at version
2.0


 -- David Krowitz

krowitz@richter.mit.edu   (18.83.0.109)
krowitz%richter.mit.edu@eddie.mit.edu
krowitz%richter.mit.edu@mitvma.bitnet
(in order of decreasing preference)