Sounds great.  I like the header and Axioms ideas.  I also am fine with the changes to Disp.  Good luck!

Yeah, the sprites right now are not clipped.  I was thinking of adding that, but I was kind of in a hurry.  That would be great if you can optimize a routine for me!  I need it optimized for size, not speed though.

I'll get working on Else soon.  You can do this in the mean time:

If <statement>
<code to do if true>
Goto 1
End
<code to do if false>
Lbl 1
Delvar 1

The asm code generated from this will be identical to the code generated when using Else.

Does that cause a mem leak like in Basic?

I can't wait to try 0.0.5!
*ZTrumpet hurry's over to download...

(Thanks Galandros!  ZTrumpet gives Galandros a cookie...)

I had an idea!
Can you make a "screen to buffer command", in which the buffer is updated with the current screen?
Also, where is the buffer? Is it the AppSaveScreen? (That's the only place I can think of now, but I've probably only got a 25% chance of being right...)
Thanks!

You can still leak in Axe Parser, but only by calling a subroutine that keeps calling itself in a non-terminating infinite loop.  I mean, you can have subroutines call themselves if you want to have a recursive subroutine, but it has to actually exit somewhere.  All the other commands are leak-proof unlike basic.

Great!

Btw, the buffer is stored in plotSScreen.

Thanks!

What would be the use of copying the screen to the buffer?  All of the drawing commands draw to the buffer anyway.

I was thinking that if you had a basic program that calls an Axe program, then somehow you'd want to be able to put the screen on the buffer.  This is to allow interactions with the screen with an Axe program as a subroutine.  Does this seem like a good idea/reason?  Thanks!

I wish I could name labels and strings and pictures of arbitrary length!  The problem is that the calculator has EXTREMELY limited memory.  Each individual label currently takes up 5 bytes.  That is 2 bytes for the location the label is pointing to, 1 for the type, and 2 for the letters.  I need these to be in a continuous array in ram.  The largest free ram is 768 bytes and so rounded to 750, that's exactly 150 Labels.  If each label was 7 letters, you would only be allowed 75 labels.  Unless I can somehow figure out how to read and write data directly to ROM, there really just isn't enough memory to keep track of long names.

Ah ok well I was just thinking...you could set it up so that if it jumps to a label or calls it, instead of having labels stored you can parse the location of the label instead into the goto, kind of like assembly is done.