Darl gave me before a routine to display a text on the screen but that wasn't really what I was looking for so using Axeguess example, I've been trying to get input from user as follow:
1. "Input Number" is displayed on the screen
2. Number is input until user presses Enter
3. Number input is displayed on the screen

This is what I've come up with so far, I use 3→{length(A)+A} to add a byte at the end of an existing number in the memory like using lists in BASIC. 3→LX(1+dim(LX, if it works

.INPUTNO
"Input Number"→Str0
ClrHome
Disp Str0

sub(I)
Disp A,i
If getKey(15)
ClrHome
End

Lbl I
0→A
getKeyüK
Repeat getKey(9)
If K=36:7→{length(A)+A}
If K=35:4→{length(A)+A}
If K=34:1→{length(A)+A}
If K=28:8→{length(A)+A}
If K=27:5→{length(A)+A}
If K=26:2→{length(A)+A}
If K=20:9→{length(A)+A}
If K=19:6→{length(A)+A}
If K=18:3→{length(A)+A}
End
Goto I

I got an ERR: MISSING END during the compiling. Any help?

Edit: AXEGUESS in Axe 1.0.1 is exactly the same as the code in Axe 0.5.3 so I don't think it's outdated.

if I have an infinite loop in my application, is there a quit button like ON in Basic? and not having to take out the batteries?

No, but doing Repeat Getkey(15) will loop until you press clear. I hope all these answers are helping you

Squidgetx made that routine, so idk really
But iirc what length() does is it goes through data until it reaches a zero, then returns that number.  If this is looped and used properly one could skip a definable number of [00]s, which the programmer could put in to separate strings and such.

Something to remember: Axe and basic are completely different.  The only thing they share are the editor and the tokens.  So a good part of the stuff that works in basic won't work in Axe, and vice-versa.


So waht you're trying to do with this is just have one number be put in, or a string of numbers?  Because the code above will only store one number to the variable. (actually I don't see the point of using length() in this, what are you trying to do with it?)

Goto A would jump to Lbl A.  Repeat getKey(15):End waits until the user presses clear.

As for the code, A is always increased, not just when a key is pressed.  What might work is checking if the byte is non-zero, after the byte is stored.
Also I would change lines like this If K=36:7→{N+A}End to If K=36:7→{N+A}:End.  There's more optimized ways to handle it, but the way you have it works enough.
Btw numbers in axe/asm can only be up to two bytes.  trying to make a three-byte number won't work.

Axe is a lot less complicated than asm, but has some of the same concepts (pointers, data, etc)

Shade().

To restore the OS's original contrast before you quit, use Shade(Shade()).  I've specifically optimized this nesting.

Goto A would jump to Lbl A.  Repeat getKey(15):End waits until the user presses clear.

As for the code, A is always increased, not just when a key is pressed.  What might work is checking if the byte is non-zero, after the byte is stored.
Also I would change lines like this If K=36:7?{N+A}End to If K=36:7?{N+A}:End.  There's more optimized ways to handle it, but the way you have it works enough.
Btw numbers in axe/asm can only be up to two bytes.  trying to make a three-byte number won't work.

Axe is a lot less complicated than asm, but has some of the same concepts (pointers, data, etc)

Actually, Runer wrote a library that lets you add, subtract and display 3 byte numbers.

"55" is a string when looked at in a text format.  Once it is compiled, it will correspond to the actual 55, but each character is one byte in text format.  The ASCII equivalent of 5 on TI-8x calcs is 35.