I was thinking something along the lines of this.  I whipped it up in about an hour:

This is amazing!  I never realized i was in basic.  When I put it on my calc today, it errored because it is in Basic, and basic is not ran "Asm(prgmAHEX".
Excellent job on this Quigibo!

The Asm( code parser needs a way to insert pointers to variables, methinks.

btw I do hope Asm( in axe will not have the slow loading that hinders the BASIC version of it . In BASIC, the lower your RAM, the longer it takes for an ASM program to even startup at all with Asm( and it's even worse with many files on your calc. Again, thought, maybe you won't have this problem since the ASM code would most likely be included inside the Axe program, not as an external program, requiring searching the entire VAT for it (which is what slows down Asm( that much in BASIC, I think). An example of how slow Asm( can be is The Reign Of Legends 3 map loading. Each Asm(prgmCODEX instructions takes about 0.25 seconds to execute. Not too bad for a one-time execution, but it's another story when you are using it in a loop.

Unfortunately no, I haven't been able to spot a pattern in the errors yet, but I haven't done a rigorous debugging either.  I'll do that tomorrow probably.

That's already been done.  It will be in the next release coming very soon.  You have to manually store data though since I haven't added automated data structure support yet.  I'll explain what I mean by that when I release it, but basically you have to keep track of the size of the array, dimensions of the array, and maximum size of the array yourself.

Yeah, you won't even need a title screen to hex program because when do I add splash screen support, it will just use the calc's pictures and copy the ones you choose into the program.  If you need more than 10 pictures you can always write them in Hex if you're really desperate, but I think there are some Pic-to-AppVar programs out there and I might support AppVars where you normally enter a picture.  Grayscale will take a while but I can't think of a good syntax for it yet...

Copy means copy during compile time of course

The way grayscale will work will be that all drawing routines actually draw to both buffers at the same time.  When you use DispGraph in grayscale mode, or maybe it will just be a different command, It displays the first buffer mixed with half of the second buffer.  Then the next time its called, it automatically switches to using the other half of the second buffer.  It will not automatically be gray.  You have to constantly redraw the screen in the main loop.

You can automate that when I add interrupt support, but I'm nowhere near ready for that now.