Xref: utzoo comp.sys.ibm.pc:30075 alt.msdos.programmer:130 comp.lang.c:19300
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!shelby!helens!relgyro!mike
From: mike@relgyro.stanford.edu (Mike Macgirvin)
Newsgroups: comp.sys.ibm.pc,alt.msdos.programmer,comp.lang.c
Subject: Re: MS QC _getimage()
Keywords: how does it work?
Message-ID: <231@helens.Stanford.EDU>
Date: 12 Jun 89 18:28:43 GMT
References: <Jun.11.13.28.35.1989.24006@topaz.rutgers.edu>
Sender: news@helens.STANFORD.EDU
Reply-To: mike@relgyro.STANFORD.EDU (Mike Macgirvin)
Organization: Stanford Relativity Gyro Experiment (GP-B)
Lines: 25

In article <Jun.11.13.28.35.1989.24006@topaz.rutgers.edu> jjoshua@topaz.rutgers.edu (Jon Joshua) writes:
>
>In MS QC 2.0, _getimage() and _putimage() are great ways of blasting
>data onto the screen.  I was wondering how the data is kept in memory.
>I want to be able to create a screen in memory and the use _putimage()
>to display it.  It would seem that _putimage() was only meant to be
>used with data from _getimge().
>
>Does anyone have any info?
>
	The data is stored as
	int	[2 bytes]	width * depth
	int     [2 bytes]	height
	unsigned char image[]   depth * width * height bits of image

	I have succesfully used the _{get,put}image arrays for my own use,
with the following limitation: the depth info. Since the depth changes with
adapter types, you must limit your program to working at a particular
depth, or make sure that when you use the buffer yourself, you place
the info in it correctly. I'd love to get my hands on the source, since
these routines are so darn FAST!
	-------------------------------------------------------
	     "There must be some kind of way out of here." 
        Mike Macgirvin - mike@relgyro.stanford.edu (36.64.0.50)
	-------------------------------------------------------