Mail Archives: djgpp/1997/01/26/08:28:22
In article <Pine DOT SUN DOT 3 DOT 91 DOT 970123164053 DOT 562L-100000 AT is>, Eli Zaretskii
<eliz AT is DOT elta DOT co DOT il> writes
>
>On Wed, 22 Jan 1997, Moo-Juice wrote:
>
>> but whenever I search through the FAQ I always seem unable to find the
>> relevant information I require... maybe its just me, or maybe it is just
>> obscure headings.
>
>Did you try to use the indices at the end of the FAQ? If so, and if they
>seem obscure, I'd like to hear suggestions on how to improve them.
I'll have a look at them, and tell you what I think. I'm not one of
those to question anybodies documentation layout/construction as it is
not one of my most favourable traits either <g> But I will have a look
for you. When people suggested reading the FAQ, which I duely did, I
was looking for something along the lines of 'accessing screen memory -
you do it like this in DJGPP rather than like this in your bog-standard
c/c++ compiler'.
>> 1. The project I'm working on, will be text only. For this reason,
>> I wish to be able to switch between 80x25 & 80x50 video modes. Is
>> it simple just to support these two modes? Which calls would I
>> need to set these, or other text modes?
>
>You should read the library documentation for all the functions of the
>"conio" family. From the DOS prompt, type the following words of wisdom:
>
> info libc func conio
Yes, I looked at them, and for the time being I have indeed used them.
Unfortunately, they do not meet my requirements. I basically have to
use ScreenPutChar or ScreenPutString. I also need functions to copy
larger amounts of data (not just a line of text with the same
attribute), and so am looking for a method to access the screen directly
as a pointer, so I can just copy an array across, or use a movedata()
function as previously suggested in this thread. The conio functions
seem a little too slow, so if any has any source code to get me a
pointer to the video mem, and setting 80x25 or 80x50 modes I would be
very grapefruit <g>
The reason I can't use something like 'ScreenUpdate()' is because it is
a text-based windowing class, and i can't just plonk information on the
screen as a window might be obscuring it, so this has to be checked
first.
--
Moo-Juice
- Raw text -