I think something like the [Pic0]->Pic0 code kinda thing would be uber awesome if it also supported appvars. Like, you have an appvar with all your levels for your game, in appvLEVELS, and you want to package your program as an app with no huge appvars, so you say: [appvLEVELS]->GDB1, and it absorbs the appvLEVELS into the compiled App, and puts a pointer to the start of the data in GDB1. Does that make sense?

Would it actually be possible to make midi instruments? If not, I suggest at least having sine, triangle, and square as options.
I am on a serious page starting streak.

Sadly, the calculator can only do PWM.  (Each speaker is only 1 bit, unfortunately.) He can add PWM and FM synthesis with PWM, though.  With PWM, you can change the volume of the tone.
If he doesn't make it a feature, I will make an Axiom for it.  ...Eventually.

EDIT: With extra hardware, you can generate other wave forms with the square.  You can also add a resistor to make the two lines a simple two-bit DAC and have a closer approximation, or you can make a square to triangle wave circuitry and add a lowpass filter to turn the square wave into a sine wave.  In reality, only a few people would actually make the hardware, so I'm not really sure how practical it would be. 

Why line drawing doesn't have clipping is something that has baffled me and I think many other Axe coders for quite some time. I know of multiple great games just off the top of my head that don't look quite right because lines don't clip if partially offscreen. I know coding the clipping is definitely doable, so that's not the issue. The only issue might be the added size and speed overhead of the clipping. But even if this is a big issue, this could be solved easily enough by keeping the current line command as-is while adding a separate line command that clips and then calls the standard line routine. Either way, I'm sure many Axe programmers would be very happy to see line clipping implemented.

Quote from: Runer112 on October 08, 2011, 01:31:52 am

Either way, I'm sure many Axe programmers would be very happy to see line clipping implemented.

* JustCause raises his hand and nods approvingly

Jump! Jump! Jump Around!

Line clipping actually IS very difficult.  there are 2 ways to do it, either pre-clip and then use the routine normally, or clip every individual pixel that would be on the "virtual" line so all that's left is on the screen.  That second option is what I used to do when lines were clipped in the past, but this was more than twice as slow and could only work with one buffer (like the circle command currently, and for the same reason).

To take the first option and actually compute new boundaries for the line involves a lot of extra math, needing several calls to the multiplication and/or division routines.  The speed at this point would most likely be at least as slow as doing the pixels individually and way WAY bigger.  I want the line clipping very badly as well but its not exactly an easy fix to make unless it becomes an extremely specialized command.

^^^ Good idea!
And what is line clipping?

Instead of the line not being drawn when one part of it is off the screen, the part that is onscreen is drawn.