ftp.delorie.com/archives/browse.cgi | search |
Xref: | news2.mv.net comp.os.msdos.djgpp:2483 |
From: | gfoot AT mymail DOT com (George Foot) |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: GRX20 Help! |
Date: | Fri, 05 Apr 1996 21:24:35 GMT |
Organization: | UnipalmPIPEX server (post doesn't reflect views of UnipalmPIPEX) |
Lines: | 18 |
Message-ID: | <4k3vit$20m@soap.news.pipex.net> |
References: | <4jvajm$9nj AT news DOT umbc DOT edu> <4k09t7$geq AT news DOT cea DOT fr> |
NNTP-Posting-Host: | am078.du.pipex.com |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
o'toole casey wrote: >Second.. Is there anyway to access the memory of the buffer directly so I >dont have to use the putpixel function everytime? and nicolas AT dsys DOT ceng DOT cea DOT fr (Eric NICOLAS) replied: >In the GrContext datas, you have somewhere a gf_baseaddr which is the adress >of the screen. But be aware that you'll have to manage *far* pointers, which >is not obvious with gcc. PutPixel and others libgrx functions are REALLY fast, What's this about far pointers? I thought they didn't exist under gcc. AFAIK all pointers are capable of specifying any memory address... the far keyword is not defined... George Foot gfoot AT mymail DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |