Subj : Re: cputs does not work in graphics-modi ?
To   : borland.public.cpp.borlandcpp
From : R.Wieser
Date : Sun Sep 11 2005 12:55 pm

Bob Gonder <notbg@notmindspring.invalid> schreef in berichtnieuws
8cv5i1h957houhkmp6i52la871u4414ohr@4ax.com...
> R.Wieser wrote:

Hello Bob,

> >> "Not correct"  now, or back when the compiler was new?
> >
> >Would be a bit difficult for me to look to "back when" would it not ?
>
> No, quite easy. Look at the documentation from "back then".

Ohhh ....    You mean if the docs match.    Alas, as I mentioned, my
compiler is a bit light documentation-wise.

> >But do you think that mode 12h (driver=vga, mode=vgahi) would have
changed
> >in between ?   As far back as I can see mode 12h has allways been 80x30
text
>
> No, it has always been listed in the manuals as  640x480
> graphics mode.

Should I be offended, or should I grin ?.   Graphics mode 12h lists (in
multiple documents) 80x30 as text-size.  I assumed that you allready knew
that I was aware that mode 12h was & is a graphics-mode.

> >> If you are choosing a screen mode that doesn't support those
> >> functions, then there is no surprise that they don't do what you want.
> >
> >You're assuming something I didn't.   But it actually does not matter :
>
> No, I'm assuming that what you are saying is what you are doing.
> Mode 12h is a graphics mode, and is being used with text commands,
> which is not "supported" by the C language.

Would you care to supply some body (documentation) to the above "it doesn't"
?   I don't respond too well to stuff that looks like "findings converted to
'facts' " (bugs with seniority).

> >Am I hearing a Gates-adept here ?   "new versions are better than old
> >version, whatever the reason" :-)
>
> New version support new hardware.
> You'll have a Dickens of a time getting BCC to support 5GB files.

.... which is the opposite of what I'm trying to do here.  In other words :
Bad example.

> >I'm sorry ?   The bios console-output works without any problems (after I
>
> cputs() is documented to write to a text window, not a
> graphics window.  It is documented to be able to use
> Bios calls to do so. It is Not documented that said Bios
> calls will work on graphics screens.

Sorry, but you are playing dumb here


You see, it *is* documented that those bios-calls will write to a
graphics-screen.  But I grant you that you won't find a description of the
(video) bios-calls in the documentation of your compiler.   They have no
place there (are seperate documents).

> That bios console-output "happens to work" on a graphics screen is a
> nice feature from the people who wrote the Bios, but is not a
> documented feature of BCC.

<sigh ....>

> Other way around.
> cputs() is the work-around.
> outtext() and outtextxy() are the proper methods.

<grin>.   If you want to see it that way.  To me it's just fancy,
resource-wasting (especially when looking at way-back-when machines) stuff.

Regards,

.