Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!uakari.primate.wisc.edu!indri!polyslo!csun!csuna!abcscnuk
From: abcscnuk@csuna.csun.edu (Naoto Kimura)
Newsgroups: comp.lang.pascal
Subject: Re: Saving screen images to disk, can y
Message-ID: <2160@csuna.csun.edu>
Date: 25 Aug 89 23:44:40 GMT
References: <5425@decvax.dec.com> <208300009@s.cs.uiuc.edu>
Reply-To: abcscnuk@csuna.csun.edu (Naoto Kimura)
Organization: CSU Northridge
Lines: 29

In article <208300009@s.cs.uiuc.edu> mccaugh@s.cs.uiuc.edu writes:
>
>It would seem that the built-in Procedures:
>
>	GetImage (x1,y1, x2,y2: word;  VAR bit_map: untyped)
>
> ... (text deleted) ...
>
>	PutImage (x,y: integer;  VAR bit_map: untyped;  bit_blt: word)
>

Make sure that you use the ImageSize function for finding out the
number of bytes to allocate for the buffer.  This way if you are using
a different mode or a different display, you won't have to allocate
more memory than necessary.  For those who want to know, the function
header is as follows:

	FUNCTION ImageSize( x1,y1, x2,y2 : Word ) : Word;

Be careful when you're some of the high resolution modes of some
displays because the amount of memory can exceed the 64K-15 byte limit.
In such cases, you'll have to save the graphics screen into several
smaller pieces.

                //-n-\\			 Naoto Kimura
        _____---=======---_____		 (abcscnuk@csuna.csun.edu)
    ====____\   /.. ..\   /____====
  //         ---\__O__/---         \\	Enterprise... Surrender or we'll
  \_\                             /_/	send back your *&^$% tribbles !!