Runs exactly the same speed on all three (four?) calculators! Wow.

Cool, I might try it out. Since it's in basic, I might port it to the 68k series, but I don't know if the xLIB application is available for the 68k series as well. Does anyone know?

I wouldn't think so, but you could use flib.

What's flib?

Flib is a library that is sometimes used by BASIC programmers to do C/ASM functions such as grayscale.
I believe that it is like your "X-Lib", although is is not a flash application.

As well as nice drawing.

I bet it's possible with pure basic on the 89... being a pure basic fanatic, I would find that preferable.

Yea.. I don't really like for BASIC programs to utilize ASM tools.. I never use them myself.. partly because I like to have the program all in one file.. I've only used Omnicalc [which is an APP, so it doesn't really count :-P..]to make sound in one of my programs <plug class="pointless"> http:// www.ticalc.org/ archives/ files/ fileinfo/ 354/ 35424.html </plug> :-D

Using flib in Timerize is actually decreasing the number of included files significantly.

Not the grayscale.

That's what I was thinking. I am very good at basic for both z80 and 68k (I have a TI-83 Plus Silver Edition and a TI-89 Titanium) and I have never seen a command for grayscale in the catalog for either calculator.

It doesn't work for many pixels at one time, but:

Repeat getKey=105
Pxl-On(A,B
Pxl-On(A+1,B
Pxl-On(A,B+1
Pxl-On(A+1,B+1
Pxl-Off(A,B
Pxl-Off(A+1,B
Pxl-Off(A,B+1
Pxl-Off(A+1,B+1
End

That's a gray square..
Also, this could be:

Repeat getKey=105
Line(A,B,A+.2,B
Line(A,B+.2,A+.2,B+.2
Line(A,B,A+.2,B,0
Line(A,B+.2,A+.2,B+.2,0
End

Which is somewhat smaller [I don't know about speed..] but not by much..

Like I said, this doesn't really work that well with many pixels at one time..

It even works on my 83+ normal. Flickery, but effective. Just like most CRTs.

Of course, it's not pure BASIC, but you could always use the sprite() command from Omnicalc and switch them back and forth.. example:

Repeat getKey=105
sprite(1,0,0,8,8,A,B
End

To execute that, Omnicalc should be installed and the sprite you want to make grayscale is at (0,0) in Pic1 (which can be archived if desired)

This will make every pixel gray though.. if you want to display some black or in there, another sprite() command is needed after the 1st one.. at the end of this command add a ",2" [without quotes] and it should make every pixel that is on in the 2nd sprite be black so long as it isnt overlapped by the first sprite.. this code will make an 8x8 gray box with a black outline:

[
Pic5 contains this data at (0,0):
.db %00000000,%11111111
.db %01111110,%10000001
.db %01111110,%10000001
.db %01111110,%10000001
.db %01111110,%10000001
.db %01111110,%10000001
.db %01111110,%10000001
.db %00000000,%11111111
]

Repeat getKey=105
sprite(5,0,0,8,8,20,20
sprite(5,8,0,8,8,20,20,2
End

Wow.. long post.. my bad about that..

Do you have a TI-84 SE?

None on there, either.

I have an 83+ SE and an 89 Ti

will this work on a ti-84+??? i just wanna play ddr on my calc

its supposed to, most people tried it and it worked. I dont have a 84+ so I cant test tho :P

CyclePic, on the 89, works well enough for a sort of grayscale. Plus, it's not like there's "grayscale commands" in assembly, it has to take some work from the programmer.

Now that I think about it, that wouldn't be that hard. The TI-OS restricts the 83+SE, the 84+, and the 84+SE to 6MHz like the 83+, and they have to be unlocked to run at the full 15MHz.

the ZCALCVER program included with the game is what allow me to slow dowwn the game on SE calcs. it detect your calc model so if its not a regular 83+ for( loops are slowed down and animations scrolls one pixels at a time instead of two. Basically that title screen animation is smoother on faster calcs

Why is it restricted? To make the batteries last longer?