| Scott Earnes
Delphi Developer |
Wed, 18 Jun 1902 08:00:00 GMT
Re:Re - Fill whole screen
Quotesquigger wrote:
> scott earnest -
> >Look back in the posts to see where I explained why this >problem happens, and how
> >to fix it. Summary: Write your own procedure to send >messages to the screen via
> >direct video writing.
> yeah, really helpful Scott - how about someone tell the poor
> bastards who don't know just HOW to do what you suggest for
> once?
previously posted message? Puhhleeze. I had already written a followup article on
the topic in the past 24-48 hours; why should I rehash something that I already wrote
the details to and which should be readily available to anyone who has the initiative
to go look? And if you were to go back and look at that article, you'd see that in
regards to, "Write your own procedure to send messages to the screen via direct video
writing", I even did the job so that you wouldn't have to.
This group has had a long legacy of being relatively flame-free, and personally I
have always tried to be helpful and constructive. Let me just suggest that if you
feel the need to post holier-than-thou sarcastic messages, please either check it at
the door or take it elsewhere where that sort of juvenile attitude is more the norm.
And if you really have a bone to pick with someone (including myself), please take
issue in e-mail so that it doesn't clutter up the group any more than necessary.
Quote> not everyone knows every byte of memory by heart, ya know.
news software. Most software has a way to recall previous messages posted that are
still on the server. And if that's a real problem, point your web browser to
www.dejanews.com and go digging. Either way, you'll be able to find my article,
which even included a reusable function for quickly writing strings to directly to
the screen.
Quote> This is a major problem with this newsgroup, by the way - you
> lot always assume that everyone else knows just what you do.
netiquette. And if you ask a question nicely, just about any regular to the group,
and even those passing through will be glad to either a.) provide a sufficient answer
to the problem, b.) suggest ways to go about solving the problem, or c.) offer
pointers to places where the solution to the problem can be found. My initial
message in this thread fell under category A. My second message in this thread
(which you were replying to) happens to fall under category C, being a pointer to my
category A reply. If you feel the need to get your undies in a bundle over that,
then that's your problem.
Quote> const
> textscreen = $B800;
> procedure fillscreen;
> var
> x,y,q,c:byte;
> {q is char, c is colour}
Quote> begin
> for y := 0 to 25 do
> for x := 0 to 80 do
Quote> begin
> mem[textscreen:(y * 80 + x) * 2 + 1] := c;
> mem[textscreen:(y * 80 + x) * 2] := q;
> end;
> end;
> $B800 is the start of text screen memory for colour monitors -
> if you want to use a monochrome monitor (yes, they're still
> here!), uses $B000;
> The memory structure is 4000 words - one byte for the
> character, then 1 byte for its colour value. (or it may be the
> other way around - if this doesn't work, swap the two MEM lines
> above) ;)
as the CACA rule -- makes it easy to remember). Switch what you assign to each mem[]
reference.
And, BTW, on an 80x25 screen, it's 2000 words, not 4000.
Also, if you really need to know, each 80x25 text page begins at 4096-byte
increments. Page 0 is 0, page 1 is 4096, page 2 is 8192 . . . up to page 7 is 28762.
Quote> squigger hops again
Scott Earnest | _,-""-_,-""-_,-""-_,-""-_,-""-_,-" |
set...@ix.netcom.com (primary) | We now return you to our regularly |
siny...@{*word*104}space.org (alternate) | scheduled chaos and mayhem. . . . |
|
