Date: Tue, 11 Aug 1998 11:13:33 -0300 (ADT)
From: Endlisnis <s257m AT unb DOT ca>
To: George Foot <george DOT foot AT merton DOT oxford DOT ac DOT uk>
cc: djgpp AT delorie DOT com
Subject: Re: Text and graphics?
In-Reply-To: <199808092219.XAA22672@sable.ox.ac.uk>
Message-ID: <Pine.SOL.3.96.980811110938.120B-100000@sol.sun.csd.unb.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk

On Sun, 9 Aug 1998, George Foot wrote:
->> > What the hey?  `scanf' is for reading, not writing, so obviously you
->> > can't write anything using it.  Furthermore, it's unlikely to work right
->> > in a graphics mode; you'll have to use Allegro's features for that.
->>     As long as you are in an 8bbp mode, printf should work fine.
->Personally I'd rather not rely on it.  It's unpredictable where the 
->text will be printed, and you don't have as much control.
	You can use 'gotoxy(int,int)' to tell it where to put the text,
although it has a granularity of 8 horizontal pixels and 16 vertical
pixels.  And, (I don't know if Allegro suffers from this) but AFAIK any
direct screen writes (in VESA 1.2 mode) can get screwed up after a BIOS
text write.  The reason behind this is most packages buffer the current
VESA bank, and only change it when it is needed, but the BIOS call will
change the current bank and the graphix will be written in the wrong
location.  So it probably is advisable to use some other form unless you
don't care about the limited positions and you are using VESA2 LFB.

	Endlisnis
[I have a pyramid of wingyness]