It has been quite a while since I wrote a substantive TI-BASIC program!
My favorite calculator games are short arcade-style games- I think the format works particularly well on a device primarily used for other purposes because the time commitment for any individual round is low. Logical recently reminded me of his port, and I thought I'd take a stab at it in TI-BASIC.
I don't have much to show for now besides the graphics. Here's a ring. Not very interesting.
A significant issue with programs like these is that their speed depends on which hardware revision you're running it on and how full your VAT is (among other things, but these are the two most significant factors, in my experience). An exciting program on M+ can be horrifically boring on calcs made before that revision. I think I'll try to reduce the influence of this effect by forcing the base speed to be proportional to the time the program takes to draw the ring. I can only measure it to the precision of the nearest second, but this should be enough for my purposes. I consistently measure 2 seconds on a freshly-reset rev-M calculator and 5 seconds on a freshly-reset rev-C calculator.
My favorite calculator games are short arcade-style games- I think the format works particularly well on a device primarily used for other purposes because the time commitment for any individual round is low. Logical recently reminded me of his port, and I thought I'd take a stab at it in TI-BASIC.
I don't have much to show for now besides the graphics. Here's a ring. Not very interesting.
A significant issue with programs like these is that their speed depends on which hardware revision you're running it on and how full your VAT is (among other things, but these are the two most significant factors, in my experience). An exciting program on M+ can be horrifically boring on calcs made before that revision. I think I'll try to reduce the influence of this effect by forcing the base speed to be proportional to the time the program takes to draw the ring. I can only measure it to the precision of the nearest second, but this should be enough for my purposes. I consistently measure 2 seconds on a freshly-reset rev-M calculator and 5 seconds on a freshly-reset rev-C calculator.