I was bored the other day so I started making a small flea game (I remember it from when I played Runescape, it was one of the Jagex games) and I decided I needed a drawing routine to use for drawing walls while the fleas are moving (I will try to have that up tomorrow or the next day)

Here is a version of it that I made for testing, tell me if you see any optimizations or errors (besides the extra parenthesis in the pxl-on, I know =P

The program starts at 0,0 and from there it uses the keynumbers 51-95 to draw in a 5-by-5 square that you move with the arrow keys (put it in your calculator and try it out =D)


I is the x axis
J is the y axis
K is the input


Code:


Here is my favorite line

Code:



Code:
determines the 10's place (so from 5-9 for this)

Code:
determines the 1's place (from 1-5 for this)

I am almost 100% sure that it is faster and more optimized than using a bunch of if statements to find the key that was pressed and respond to it.

Code:

One thing: what is the purpose of the ans>50 and ans<100?

So the person has to press a button with a key value of greater than 50 and less than 100 to actually draw anything (so the 5th row of keys to the 9th row of keys).

It draws in 5x5 squares.

You can condense the movement commands into two lines & save a few bytes.


Code:


Seems fairly good, not sure what I would use it for, but very nice!

Wait, nevermind, Kuro already suggested that.

Yeah, that and the if statements at the end can be improved.

Is there a guide somewhere to using those types of commands? I don't quite understand but from what I can it seems that it is just a condensed conditional. Can it subtract and add other numbers than 1?

Of course it can

Here is the explanation:

If you have the code


Code:
, where * is a a comparison thingie such as =, >, <

the calculator will return 1 if the statement is true, or 0 if the statement is false.

Thus, to change it by more than 1, multiply it by some constant instead, like


Code:


Does this explain it enough? It basically treats it as a Boolean, but instead of true/false, the calc uses 1/0.

EDIT: Whoops, typo int the code

Harq: did you ever take a look at the 1337 guide?
http://www.ticalc.org/archives/files/fileinfo/369/36993.html

oooooh so it pretty much just multiplies the constant by 0 or 1 depending on whether it is true or not

Good to know =D


P.S. Yes I have, but maybe a different one than you are thinking of... (I pretty much used that to learn ti-basic =P)