home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!psuvax1!rutgers!njitgw.njit.edu!hertz.njit.edu!dic5340
- From: dic5340@hertz.njit.edu (David Charlap)
- Newsgroups: comp.os.os2.misc
- Subject: Re: 32bit graphics engine, etc...
- Message-ID: <1992Aug26.192600.2131@njitgw.njit.edu>
- Date: 26 Aug 92 19:26:00 GMT
- References: <1992Aug24.094700.21837@actrix.gen.nz> <1992Aug24.181930.21825@cco.caltech.edu> <1992Aug25.115314.20542@actrix.gen.nz>
- Sender: news@njit.edu
- Organization: New Jersey Institute of Technology, Newark, N.J.
- Lines: 21
- Nntp-Posting-Host: hertz.njit.edu
-
- In article <1992Aug25.115314.20542@actrix.gen.nz> Steve.Withers@bbs.actrix.gen.nz writes:
- >The 32-bit GRE's do the same thing as the 16-bit ones - they render the screen
- >images which the video card then displays. This is done - as I understnad it -
- >independently of what software is actually doing. The GRE performs the work
- >requested of it by the programs. The 32-bit GRE does that faster and more
- >efficiently. The impact on applications should be nil - other than to speed up
- >the display.
- >
- >No modifications required as i understand it. If I am wrong, will somebody
- >please put me right?
-
- You're right. The API will be unchanged. Your applications will not
- need any changes. They will, however, have some extra bonusses.
- Primarilly, they will have more window-object handles available,
- meaning that more icons/buttons/windows/etc will be available for
- simultaneous use - eliminating the "out of memory" errors, hopefully.
- --
- |) David Charlap "I don't even represent myself
- /|_ dic5340@hertz.njit.edu sometimes so NJIT is right out!.
- ((|,)
- ~|~ Hi! I am a .signature virus, copy me into your .signature file.
-