Sorry to hear you could not finish it. Does it mean you are done with calculator programming completely? It would suck to see you go completely.

Well... The 83/84+ series will probably outdated soon, so I'd need to learn another language in order to begin something else... And since I do absolutely nóthing informatics-related, it'd take alot of effort to learn something new again. Hopefully I'll be 'back' again, though there's just no time for me to do anything for a while. :c

I guess you could compile axe, then just optimize it a lot... but that seems inefficient

I... have zilch experience with Axe, sorry. Q_Q

EDIT:
Oh, and it doesn't really concern the 1-9 keys; it's just for 5 keys of the same group (namely Yequ-Graph). I had this other idea on how to accomplish this; will post the (probably waay to long and inefficient) routine later. <-- Failed. Using this now, but it's still not what I wanted, plus I bet it could be optimized, ghehe (BIG thanks to ThePenguin for this):
tracePressed:
push af
set 0, c
bit 0, b
PUSH BC
jr nz, traceIsHeld
LD A, 58
LD (CheckYequ), A
LD (CheckWindow), A
LD (CheckZoom), A
LD (CheckTrace), A
LD (CheckGraph), A
LD A, -58                                    ;
LD (ButtonPressed), A                   ;
CALL CheckYSprites                         ;you can ignore these in each loop, I just want this to be performed with the appropriate number stored in (ButtonPressed)
jp graphDone
traceIsHeld:
    LD A, 58                                      ;
    LD (xpos), A                                 ;
CALL sprendcall                                ; also ignore this, it's just something for the rest of the script.
LD A, (CheckTrace)
CP 58
JP z, graphdone
LD A, 58
LD (CheckTrace), A
LD A, -58
LD (ButtonPressed), A
CALL CheckYSprites
jr graphDone
zoomPressed:
push af
set 0, c
bit 0, b
PUSH BC
jr nz, zoomIsHeld
LD A, 44
LD (CheckYequ), A
LD (CheckWindow), A
LD (CheckZoom), A
LD (CheckTrace), A
LD (CheckGraph), A
LD A, -44
LD (ButtonPressed), A
CALL CheckYSprites
jr graphDone
zoomIsHeld:
    LD A, 44
    LD (xpos), A
CALL sprendcall
LD A, (CheckZoom)
CP 44
JR z, graphdone
LD A, 44
LD (CheckZoom), A
LD A, -44
LD (ButtonPressed), A
CALL CheckYSprites
jr graphDone
graphPressed:
push af
set 0, c
bit 0, b
PUSH BC
jr nz, graphIsHeld
LD A, 72
LD (CheckYequ), A
LD (CheckWindow), A
LD (CheckZoom), A
LD (CheckTrace), A
LD (CheckGraph), A
LD A, -72
LD (ButtonPressed), A
CALL CheckYSprites
jr graphDone
graphIsHeld:
CALL graphsprshow
LD A, (CheckGraph)
CP 72
JR z, graphdone
LD A, 72
LD (CheckGraph), A
LD A, -72
LD (ButtonPressed), A
CALL CheckYSprites
graphDone:
pop bc
pop af
ret
windowPressed:
push af
set 0, c
bit 0, b
PUSH BC
jr nz, windowIsHeld
LD A, 30
LD (CheckYequ), A
LD (CheckWindow), A
LD (CheckZoom), A
LD (CheckTrace), A
LD (CheckGraph), A
LD A, -30
LD (ButtonPressed), A
CALL CheckYSprites
jr graphDone
windowIsHeld:
    LD A, 30
    LD (xpos), A
CALL sprendcall
LD A, (CheckWindow)
CP 30
JR z, graphdone
LD A, 30
LD (CheckWindow), A
LD A, -30
LD (ButtonPressed), A
CALL CheckYSprites
jr graphDone
YequPressed:
push af
set 0, c
bit 0, b
PUSH BC
jr nz, YequIsHeld
LD A, 16
LD (CheckYequ), A
LD (CheckWindow), A
LD (CheckZoom), A
LD (CheckTrace), A
LD (CheckGraph), A
LD A, -16
LD (ButtonPressed), A
CALL CheckYSprites
jr graphDone
YequIsHeld:
    LD A, 16
    LD (xpos), A
CALL sprendcall
LD A, (CheckYequ)
CP 16
JR z, graphdone
LD A, 16
LD (CheckYequ), A
LD A, -16
LD (ButtonPressed), A
CALL CheckYSprites
jp graphDone
Works álmost perfectly, except that when you, lets say, hold Yequ then press the other four remaining buttons (while still holding Yequ) it won't react to any keypress untill you've released áll buttons. Then it resets.
So 'Hold Yequ' --works--> 'Press Window' --works--> 'Release Window' --works--> 'Press Window' --ignores last press --> ...
Sorry for being wordy, but hopefully someone gets it as it shouldn't be too difficult (yet I'm clueless).

Been struggling with this for a while now; the principle I'm looking for is simple and straightforward: react to the last button pressed, regardless of whatever else might be pressed or released.
So if you press '1', it perorms 'Label1' once, even if you have 2-9 held down at the same time already, or release random other buttons that were being held down before. Push the button, perform thát routine once. Nóthing more, nothing less. 
I'm sure there must be a simple way to do this, but... I'm newby. 
If anyone has any tips on how to do this, it'd be greatly appreciated!

Thanks alot in advance.

The thing is, there are 16 sprites defined as followed:
SpriteNumber .equ AppBackUpScreen
yspr1 .equ SpriteNumber+2
xspr1 .equ yspr1+1
yspr2 .equ xspr1+1
xspr2 .equ yspr2+1
yspr3 .equ xspr2+1
xspr3 .equ yspr3+1
yspr4 .equ xspr3+1
xspr4 .equ yspr4+1
yspr5 .equ xspr4+1
xspr5 .equ yspr5+1
;etc.

Now, there is the following piece of code, with input C = Xcoordinate of a sprite.
The idea is that it's loading C (thus an x-coordinate) to Sprite1, then Sprite2, then 3 etc. and after Sprite16 has been assigned, it starts over with Spr1 again. There's something glitchy, since it sometimes suddenly removes sprites from the screen (thus assigns x,y values to a sprite on the screen already). I can'tr figure out what's wrong though. Could it perhaps be because of direct input with the buttonpresses that it sometimes fails to finish this loop or something?

Script:

NextSprite:
LD hl, SpriteNumber
LD A, (SpriteNumber)
LD B, A
NextSpriteLoop:
INC HL                                ; 2x INC HL will go to the next sprite, since each HL holds X
INC HL                                ; and Y respectively of the current spritenumber
djnz NextSpriteLoop                    ; Keeps track of the current sprite
LD A, -9                             ; Set the Y position of the current sprite
LD (hl), A                            ; And save it to Sprite*number*
INC HL
LD (hl), C                            ; Save an X-coordinate to Sprite*number*
LD A, (SpriteNumber)
CP 16                                 ; After giving an X and Y to Sprite16, start with Sprite 1 again
JR Z, ResetSpriteNumber
INC A
LD (SpriteNumber), A
ret
ResetSpriteNumber:
LD A, 1
LD (SpriteNumber), A
ret

So... is there something wrong? Or are the errors caused by other factors?
Thanks!

http://clrhome.co.cc/resources/table/ (hover for size, time, and flags)[/ad]

This is what I was looking for, thanks! I've found all those other tables before too, though didn't knew how to figure the 'size' of the commands out of all those numbers... But that link you provded, Deep Thought, directly states so, so thank you! This'll certainly help somewhat.

EDIT:
Oh, just one more... the size/time of a Label?

Looks nifty, might make use of it!

This... is odd, I'm using AppDev (DWedit ?) for creating apps, but it's crashing when changing a certain macro.
This still works fine:
#define N1_R1 CALL Something1
#defcont \ CALL New1
#define N2_R1 CALL Something1
#defcont \ CALL New2
#define N3_R1 CALL Something1
#defcont \ CALL New3
#define N4_R1 CALL Something1
#defcont \ CALL New4
But as soon as I add one more:
(...)
#define N4_R1 CALL Something1
#defcont \ CALL New4
#define N5_R1 CALL Something1
#defcont \ CALL New5
It crashes. It's not the "New5" thingy, since it does the same for 6 and up, and when removing one earlier macro it does work fine with "5" and up. Now, this could indicate that the maximum number of macro's has been reached, however this is not the case. It can hold up to 1000 macros, and it's still far from. Plus, when adding many other macros it still works like a charm.
And what's even weirder, when using the macro to run a CALL containing both lines, line this:
#define N6_R1 CALL DoBoth
(...)
DoBoth:
     CALL     Something1
     CALL     New6
ret
it works fine again. Can go all the way from 1-w/e with that. (Though I guess it's faster and shorter to use the two CALLs in a row, rather than making a small routing doing both CALLs, right?). It's not the scripts which are being called either - with any other macro substituting for those it works fine. Am I missing something?

Thanks in advance!

Hmm, what about holding the calc upside down, using [On] through [Enter] to change the notes, and [Y=] to strum?

I've tried many things already, though one of the big downsides is that your screen is attached to the controller in this case. Holding it in any comfortable way results in you not being able to see the screen anymore.  Secondly, the buttend are really to densly packed to use the calc as a guitar-like controller... I've tried. 

A release would be nice ^^ Also you should add note streaks and possibly that blue glowy mode forgot what its called.

Notestreak... is possible to add I guess, though not really necessary. Also Star power won't be included, lol. Perhaps when the whole thing's done I'll make a 2.0 with the suggestions posted here implemented.

With regards to sound, I think that having a two player battle mode is far better than simply adding sound, because people could just be asked to play the MP3 at the same time.

No sound, and no 2 player mode, sorry. It's... 'something funny for a calculator', not some hardcore console release.  Plus, I'm really a noob in programming; never done anything with informatics whatsoever, it's just that on a random blue monday back on highschool I decided it'd be fun to have a guitar-hero like thingy on the TI calc, and wondered if intewebs could teach how to do so... so there.


On a sidenote, my laptop crashed and the last backup sets me back many weeks. On top of that, I'm réally buissy at the university at the moment, so a playable download thingy will have to wait for some more weeks... sorry. :'(