I'm not sure if Xeda uses this in Grammer, but the 5-8 being diagonal directions was used first (iirc) in xLib.  Normally 5-8 return nothing, much like 16 and 24.

So I can't seem to get the updated version on my calc to test if pressing all of the arrows will return 16 as a key press, so i will just upload this update, now:

Now, getKey returns theses values for these combinations:
5=Down+Left
6=Down+Right
7=Up+Left
8=Up+Right
16=All directions mashed    (supposed to work, not sure if it does)

Aaand, I figured out a simple solution to get the ! token to work for Repeat and While

EDIT: And I notice Awalden0808 has submitted a Grammer program to TICalc, too! Congrats on being the third person to do so! And it is actually kind of fun... If you are reading this, you should make it so the user has to reach the upper right pixel or something Or be surrounded on three sides by pixels or something. THen you could turn it into a game... Actually, I might do that

Sorreeee I tried to keep ReCode and Grammer pretty similar (just safer and more likely to work as expected in Grammer). Though Grammer has had a lot more polishing and a lot more features...

Awesome and good luck! Feel free to ask questions

Not yet, sorry I am trying to think of a useful key combination, but I don't know

Also, I am now trying to think of a token to use to insert and delete data from a var. The syntax I want is to have a pointer to the data, an offset, and number of bytes to add or remove.

mmm, maybe I wonder how Axe changes it tokens... ?

I think I know what 16 and 14 are supposed to be... the two keys (not existing) right of STAT, so on top of VARS and CLEAR (I know, they don't exist, but I think that these keys would belong there)

I think I would have to save I/O detection for another command
And that is what the keys would be if they existed
And as a note, all keys pressed will in fact return 16 (I finally got it on my real calc)

Aside from that, I have made a mini update to the version of MARS that I was working on It now has 3 difficulty levels. The reason I made this, actually, is because I wanted to show that appvars can act as subprograms, too. The one here is called GLEV and what it does is it lets the user select a difficulty level and set the processor speed.

The difficulties in MARS2 is changed simply by making the ship go slower for easy mode and faster for hard mode while the bullet stays a constant speed.