Thank you

I also have no idea if this is intentional or not, but shouldn't the X and Y coordinates in the drawing/text commands be reversed?
e.g in TI-basic you have output(Y,X but in Axe it's output(X,Y. It's kindof confusing 

I kindof prefer The TI-basic syntax because it's handled like matrices are, first rows and then columns.

Its that way on purpose.
most people that don't know much about ti-basic would find it to hard for pxlon(y,x)

Yeah, it was done specifically for consistency so that you don't have to think to yourself "Did this command use (x,y) or (y,x)?"

That problem with the input function I can probably fix.  I need to find where the buffer is that holds the input string so I can clear it.

Well what error is it telling you?  Or is it actualy crashing?

Yikes, you are on the latest version right? 

Another bug, but only when compiling as app.
Performing the following won't do anything:
1->{Y*12+X+GDB1}

Works when compiling for mirage or no shell, but as an app, it looks like its simply ignoring this line.

Another bug, but only when compiling as app.
Performing the following won't do anything:

Code: [Select]

1->{Y*12+X+GDB1}

Works when compiling for mirage or no shell, but as an app, it looks like its simply ignoring this line.

Actually, I don't think that's a bug. That line is a form of self-modifying code that changes the pointed to value in program memory.
Apps don't support SMC, which is why this doesn't work.

copy the data from GDB1 or whatever data into a freeRAM area, and then u can modify it as much as u want!
you could also decide to use AppVars for all the data, which could be Archived and UnArchived whenever u want.

got another bug: I can't do the following:
1->{L1}->{L5+4}
and I would really like to, because I am told that it is much more efficient this way.

interesting, that sounds like a bug to me!  Thats not supposed to happen, its supposed to return the value of what you put in.  (unless that has changed to something else??)