Here's a program I threw together in Axe for checking key groups.  It's used to check various combinations of keys to make sure they don't interfere with each other.  For example, press all of the arrows and then Graph...

Topic to reference: http://ourl.ca/7642

Enjoy, and source is included. 

Also, you may get an Err: Break on exit depending on the shell (or lack of) that you use since [On] is used to exit.  It's compiled for Ion, so it will work from all shells.

Thanks:
Quigibo - Axe Parser
Calc84maniac - [On] routine

amazing.  When i saw the title i just expected a noob showing off.  But this is great.

(i wish i had this for the etch-a-sketch

Lol I totally didn't thought about AxeCoderz. Now if MaxCoderz did not exist and if we seeked for a new name and only did Axe programming, we could almost become AxeCoderz

I wrote a really crude version of this at one point, but yours has boxes!
Nice job.

yes, the graphics are very helpful. thanks a lot, ztrumpet!

Lol I totally didn't thought about AxeCoderz. Now if MaxCoderz did not exist and if we seeked for a new name and only did Axe programming, we could almost become AxeCoderz

or maxcoderz could make an axecoderz subforum

well, each key on the calc keyboard has a bit assigned to it which is set when pressed and reset when not pressed. however, it doesnt really have it's own because(i guess?) it would take too long for the processor to go through and check a bit for every single key every time it want's to know what keys are pressed down and so the keys are instead broken into several keygroups. the processor then has to indicate which keygroup it wants to check and then which bit it want's to check. for some reason, certain combinations of keys will return the value of others when they are pressed because of this? i would have to read up on this again as the last time i did was over a year ago. thepenguin or any of the other asm programmers could actually explain it.
the purpose of this program is to display graphically what keys the processor is reading as being pressed down, which can then be compared with what keys are actually being pressed to ensure that a certain key combo that may be used in your game wont trigger another key that does something completely different.

or we could have a one big collection of programs and screenies, so if you don't know the name or existence of a prog. it can be found quite nicely.

well, each key on the calc keyboard has a bit assigned to it which is set when pressed and reset when not pressed. however, it doesnt really have it's own because(i guess?) it would take too long for the processor to go through and check a bit for every single key every time it want's to know what keys are pressed down and so the keys are instead broken into several keygroups. the processor then has to indicate which keygroup it wants to check and then which bit it want's to check. for some reason, certain combinations of keys will return the value of others when they are pressed because of this? i would have to read up on this again as the last time i did was over a year ago. thepenguin or any of the other asm programmers could actually explain it.
the purpose of this program is to display graphically what keys the processor is reading as being pressed down, which can then be compared with what keys are actually being pressed to ensure that a certain key combo that may be used in your game wont trigger another key that does something completely different.

Ah ok, gotcha. Guess I just don't really use Axe/assembly enough to really run into this issue.