You need to display the screen with DispGraph. Commands such as Pt-On don't draw directly to the LCD, but rather to L6, the buffer.

Update:

I have reading and writing to ALL external variables working right now, I just need to find a clever way to create and delete them.  I might be getting rid of the delvar command used in labels and make that the delete os var useage like how it works in BASIC.

Also I got direct link port I/O working and I was experimenting with the possibility of a "WaveToAxe" converter.  Right now, at 6MHz, I can just barely make out the "It's a-me Maaario!" clip that came with realsound which is what I'm using as a reference goal.  I will update on my progress later and possibly release it if I can get some decent quality, and it seems very possible.  This is NOT an assembly routine, this is in pure Axe code with the direct port commands in 0.4.0.  Unlike realsound however, the clip is much more compressed.  The realsound clip generates a 2 page app whereas the appvar created with my converter is less than 2KB.  Hopefully I can keep it that low as I start finding ways to increase the quality.

But, here is a little problem I pose, realsound has terrrible quaity on the nspire 84 keypad, so if you are planning to base your off of realsound, then the nspire willl be an obstical

zomg 32k->2k???

still, since the appvar can't be read from flash....

well good for BE users without the massive archive space
Looking good so far

From now on, I'm going to greet people with "Hellol"

I'm changing a token name.  You know how programs have the "prgm" token in front of them?  Well, I'm doing the same thing with appvars.  The problem is that its impossible to distinguish between the lowercase "v" and the recursive "v" because they share an identical ascii character.  It has led to confusion in the past, and I think it will do so in the future so I've decided to change it to "apvr" to mimic the way "prgm" is formatted so that it is both distinguishable and recognizable as to how to use it since its interchangeable with prgm.  Thoughts?

I think that's a good idea. Maybe "appv" would work, too. I get confused a lot too and always end up almost hitting 2nd+ALPHA+ALPHA+6 by mistake

Update:

I have reading and writing to ALL external variables working right now, I just need to find a clever way to create and delete them.  I might be getting rid of the delvar command used in labels and make that the delete os var useage like how it works in BASIC.

Also I got direct link port I/O working and I was experimenting with the possibility of a "WaveToAxe" converter.  Right now, at 6MHz, I can just barely make out the "It's a-me Maaario!" clip that came with realsound which is what I'm using as a reference goal.  I will update on my progress later and possibly release it if I can get some decent quality, and it seems very possible.  This is NOT an assembly routine, this is in pure Axe code with the direct port commands in 0.4.0.  Unlike realsound however, the clip is much more compressed.  The realsound clip generates a 2 page app whereas the appvar created with my converter is less than 2KB.  Hopefully I can keep it that low as I start finding ways to increase the quality.

Nice features!

As for the sound quality for the WaveToAxe thing, it seemed fine to me in the other topic. Low quality but it seemed like Atari 2600 or something. We have to remember it's a calc after all

When I finish the Doc, I will mention which commands are safe to use with interrupts.  I think only the 4 level grayscale is unsafe, but you NEVER want to have drawing as part of an interrupt because it can interfere with a lot of other things and is very uncontrollable.  You can't really have the LCD routines interrupt driven otherwise you have to disable interrupts when drawing sprites so that the screen isn't drawn with incomplete sprites.  But that's what usually takes up most of the processing and will completely ruin the timing aspect.

Instead, you want to make your interrupt just be a timer and that's it.  That way you can have your main routine wait until its time to draw before actually drawing and only when its ready to draw.

Nope, I still can't figure it out

I'm pretty sure its just the DispGraph commands at the moment but please report if you find any more that do that!