[A83] Re: statvars...??? [Ti83+]
[Prev][Next][Index][Thread]
[A83] Re: statvars...??? [Ti83+]
Yes. It copies each byte to the LCD and then puts the new byte in its place.
Not too hard to make with some proper optimizations, such that it isn't too
much slower to draw a tilemap than to just output the screen to the port! My
point was simply that greyscale on 82/83/83+ can hog resources unless it's
tailored to the task at hand. But then you couldn't make it a component of
the C package.
I did mean LcdBusy in the other message, TI's provided wait routine.
RestoreDisp would also work, and GrBufCpy sound like it might also work but
I don't know what that is.
Assuming the 83 is similar to the 85, then this info may help about port 3:
http://www.ticalc.org/pub/text/calcinfo/ti-ports.txt
Do pardon me if you only needed 83. It seemed as though you would eventually
have support for 83+ as well. I shall refrain from answering people's
problems as I (mis)perceive them, since it appears my perceptions are so
greatly offensive.
-----Original Message-----
From: assembly-83-bounce@lists.ticalc.org
[mailto:assembly-83-bounce@lists.ticalc.org]On Behalf Of Henk Poley
Sent: Saturday, July 07, 2001 2:01 AM
To: assembly-83@lists.ticalc.org
Subject: [A83] Re: statvars...??? [Ti83+]
(I couldn't find the routine on my PC, and hadn't time to go into the
internet...)
So this tilemaproutine, copies the previously generated screen to the LCD
while making a new one? Must have been some trouble to make...
You also needed to make use of a tilemaped game/program to make this work
off course...
Okay we do have spriteroutines, but they are variable width/height
spriteroutines (tilemaps need fixed sized sprites). And the other graphics
routines are ones to draw circles, fill parts of the screen, etc. Not
really things where a tilemap-routine would be handy...
It can be something to think off for putting into the compilers-library
(but not for greyscale I'm afraid).
Henk Poley
References: