Suggestion:

-The ability to store directly to the back buffer, without having to go through storing the lcd to buffer first. It migth be very useful if we want to store to the back buffer but not want to lose our main buffer content

I just remembered one more:

The ability to display the graph buffer using different logics other than OVERWRITE, like XOR.

Imagine, for example, you have a game with scrolling, but want to display a HUD. Everytime you scroll, you are forced to redraw the entire HUD, because it scrolls as well. In xLIB xLIB Revolution, the HUD is XORed right before scrolling, then XOR'ed again after scrolling (and other stuff) is done.

I also think we need the And, Or, Xor, and Over-write commands when dealing with pictures.

+1

I do believe he will add that in eventually though.

I second the last 6 posts

I doN't think he is planning to add features involving support of external ASM lib for BASIC programmers such as Omnicalc, xLIB, Symbolic and Celtic, though, meaning most likely no Omnicalc fonts. Plus since text is much slower in ASM than graphics, partially due to TI's slow txt routines, it would nearly defeat the point of using Axe. Maybe a custom font routine reading from Omnicalc font files could be done, though, using a custom sprite routine.

A ToneOut(length,frequency) command sounds awesome!

Ion header support, maybe?

Quote from: ProphetsDementia on March 14, 2010, 11:40:34 am

I CAN HAS EASTER EGGS?

How exactly could easter eggs work for something like this? Pressing some random key sequence in the app lets you play a game of Tetris?

I like that idea