Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!spool.mu.edu!think.com!paperboy!hsdndev!husc6!purdue!haven!adm!news
From: CDCKAB%EMUVM1.BITNET@cunyvm.cuny.edu ( Karl Brendel)
Newsgroups: comp.lang.pascal
Subject: Re: Turbo Pascal Graphics. HELP!
Message-ID: <25912@adm.brl.mil>
Date: 11 Feb 91 15:19:38 GMT
Sender: news@adm.brl.mil
Lines: 29

In article <1991Feb10.031517.26075@maytag.waterloo.edu>,
  dmurdoch@watstat.waterloo.edu (Duncan Murdoch) wrote:

In article <1991Feb8.060006.1333@uwasa.fi> ts@uwasa.fi (Timo Salmi) writes:

>>The obvious solution is to save the screen in parts, each one < 64K.
>>It is simple as that.  And it works.  Usually four parts is enough,
>>but this naturally depends.
>
>The trouble is that the Imagesize function returns a word, so you're
>never quite sure that you haven't miscalculated, especially if
>you're trying to write a device-independent program.  What if
>someone wants to run it on a machine with a 1024x1024 screen, with
>24 bits per pixel?

According to the 5.X Ref Guide, if the returned value of ImageSize
should equal or exceed 64K, it is returned as 0 and GraphResult will
return -11. If that is correct, you can be quite sure you haven't
miscalculated if you check for a 0 return from ImageSize.

(I Am Not A Graphics Programmer and just report what the manual
says.)

+--------------------------------------------------------------------+
| Karl Brendel                           Centers for Disease Control |
| Internet: CDCKAB@EMUVM1.BITNET         Epidemiology Program Office |
| Bitnet: CDCKAB@EMUVM1                  Atlanta, GA, USA            |
|                        Home of Epi Info 5.0                        |
+--------------------------------------------------------------------+