Message-ID:	<F77915E7F086D31197F4009027CC81C90DBF0F@probe-2.as-london.acclaim.com>
From:	Shawn Hargreaves <SHargreaves AT acclaimstudios DOT co DOT uk>
To:	djgpp AT delorie DOT com
Subject:	Re: fprintf() and using under graphic modes
Date:	Thu, 25 Nov 1999 16:01:51 -0000
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2650.21)
Reply-To:	djgpp AT delorie DOT com

Chaos writes:
>> I think it would be more robust to read this directly from the VESA
>> driver: this can be found in the mode information structure
>
> Thank you very much for that. All is need to be done is to check if this
> condition is true, and then decide to use fprintf or
> self_made_drawing_texts_func.

But since you have to write your self_made_drawing_texts_func() in
any case, why not just always use this no matter what the VESA driver
reports? I think that is better than using the BIOS text printing
routines, for several reasons:

- Much faster.

- Allows you to draw text anywhere you like, rather than only on
integer character boundaries, so you can do smooth pixel scrolling.

- Easier to control the color of the text.

- Avoids problems with different DOS versions having different
character sets, depending on the country (if you supply the font,
you can always be sure the characters will come out looking as you
expect).


	Shawn Hargreaves.

- Raw text -