Path: utzoo!attcan!uunet!zephyr.ens.tek.com!uw-beaver!rice!sun-spots-request
From: canon!laukee@nsfnet-relay.ac.uk (David Lau-Kee)
Newsgroups: comp.sys.sun
Subject: Pixrect line padding
Keywords: Windows
Message-ID: <3789@brazos.Rice.edu>
Date: 29 Nov 89 18:53:54 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 19
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 8, Issue 217, message 12 of 23

(a) Am I missing something or is the

	#define MPR_LINEBITPAD 16

in <memvar.h> for post Sun 2 machines wrong?  My 4.0.3 documentation says
that for pixrects of width > 16 scan lines are padded out to a 32 bit
boundary.  This means that MPR_LINEBITPAD ought to be 32, and that the
mpr_linebytes macro (which will take your *actual* width and depth and
return the number of bytes you need to hold a whole line) gets it wrong
(unless your bitmap happens to be < 16 bits wide or a multiple of 32!).

(b) On a cg9 with GP2 running on a 4/370 under 4.0.3 sunview windows leave
nasty trails when I open and close them.  Looking through the
documentation on the CG6 (for 4.0.3) I see that similar glitches are cured
with patches available from Sun.  Q. Are these CG9 glitches related to the
CG6 ones (seems unlikely given the differences between the two), and does
anyone know where/if fixes are available?

	-- David Lau-Kee