Xref: utzoo comp.sys.ibm.pc:30055 alt.msdos.programmer:129 comp.lang.c:19292 Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ames!apple!bloom-beacon!bu-cs!bucsb!adverb From: adverb@bucsb.UUCP (Josh Krieger) Newsgroups: comp.sys.ibm.pc,alt.msdos.programmer,comp.lang.c Subject: Re: MS QC _getimage() Message-ID: <2631@bucsb.UUCP> Date: 12 Jun 89 14:37:37 GMT References: Reply-To: adverb@bucsb.bu.edu (Josh Krieger) Followup-To: comp.sys.ibm.pc Organization: Boston Univ Comp. Sci. Lines: 18 In article 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(). The same functions exist in Turbo C (however, it is possible they may not be handled the same way). Anyway, Turbo C stores the length and width of the image in the first four bytes of memory containing the image. It's stored low byte, high byte, low byte, high byte. I'm not quite sure whether the width or the length is specified first. You can test if this is the case in Quick C by using getimage on an area of specified size and seeing if the first four stored bytes coincide with your request. -- Josh Krieger