You would probably have to change them to this to preserve the actual LCD buffer.

A) expr(L3,L6,768):DispGraph:expr(L3,L6,768)

And do this, since he was asking to store from the LCD, not the buffer.

B) expr(L3,L6,768):StoreGDB:expr(L3,L6,768)

However, it could be nice to have some built in commands for this.  Perhaps StoreGDB # with different numbers meaning different  buffers?

You would probably have to change them to this to preserve the actual LCD buffer.

A) expr(L3,L6,768):DispGraph:expr(L3,L6,768)

And do this, since he was asking to store from the LCD, not the buffer.

B) expr(L3,L6,768):StoreGDB:expr(L3,L6,768)

However, it could be nice to have some built in commands for this.  Perhaps StoreGDB # with different numbers meaning different  buffers?

Is it still safe, though? I guess it might be since:

L3 = 768 bytes (appBackUpScreen) Volatility: MED (Saving to back-buffer will corrupt)
L6 = 768 bytes (plotSScreen) Volatility: HIGH (Any buffer drawing will corrupt)

But I want to make sure that before using your suggestion (or SirCmpwn's), I won't run in any further problems, later, doing some stuff with these pointers

But I want to make sure that before using your suggestion (or SirCmpwn's), I won't run in any further problems, later, doing some stuff with these pointers

Well since L3 and L6 are the backbuffer and the main buffer, i should think so, but you'd have to check with Quigibo o.O Using built in routines would indeed be safer

I would really like some sort of fps counter or something, so you can see how your code handles differing amounts of objects and such.

True, though if there was some way to do that on 83+'s that would be nice, even an approximation.

I also would like the ability to use ElseIf:

++ ElseIf
Also, speaking of ++, I would like to see ++ and -- implemented, and possibly +=, -=, *=, /=.

I've been meaning to write another routine for accessing user variables.  I'll post it when I get around to it.

The ++ and -- are already supported.  You just write them as +1 and -1.  The compiler automatically optimizes them to the increment.  ElseIf is a possibility, I forgot about that.  A FPS counter is something you could do with interrupts.

Okay on the +1 and -1, thanks.  Also, FPS requires you to know when a second (the S in FPS) has passed.