I've got a feature request.

Would it be possible to make 'checkpoints' in the program editor and be able to jump between them using something like 2nd+Right/Left? Just wondering because my code is getting really long and it takes a while to scroll all the way to the bottom just to change 1 or 2 things before compiling again.

Also, for the Error scrolling, wouldn't it be better to scroll to 7 lines before the line with the error, so that it is at the bottom instead of the top? That's how the TIOS does it. I always have to scroll up to see what I wrote to cause the error.

That's another direction I might be headed eventually.  I might just make full fledged editor improvements to the TI Program editor during Axe Edit sessions like "sprite previews" of hex code, "bookmarks" in the code (which is what you're talking about), maybe a "Condensed View" in which labels have little plus signs next to them that expand and hide the code for each subroutine, these are just ideas I'm throwing out there.  They are all possible with the clever use of Key Hooks.  I'm just not sure if I want to go that far until I finish more commands and features, it might be an Axe 2.0.0 thing.

In fact, I would like to turn this thread into a poll, so if any administrators reading this can do that, that would be great.  After each update, I will edit the poll to list several choices of major features to include in the next update so I can get a sense about what people want me to do first.  Also, while you're at it, could you unsticky the token poll since that's already been resolved.  Thanks! 

At the bottom of the topic, you see the REPLY | NEW TOPIC | etc stuff, right? If you click the "ADD POLL" button you can append a poll to this topic. If that button doesn't show up, let me know in this thread about what you want the question to be as well as answers, and I may try to add it (or someone else could)

can you elaborate on which each option really means in terms of axe growing?

Keep in mind Axioms would be against the contest rules, though (since they would not be Axe native code). Just as an head up for contestants.

Interrupts would be nice

What are these axioms ??

Oh and interrupts too

I voted for interrupts, as they will still be native Axe yet will be very awesome. (Interrupt routines ftw!)
What would also be nice is to be able if the interrupt was caused by the ON key or by something else (the hardware timer, etc.)

I think inline BASIC is the most desired feature for me, it would make the transition a lot easier. However, how do you plan to address the homescreen, since it is unusable in regular axe?