minor question.

which is faster, pxl-Test(X,Y) or this:

Code: [Select]

.eulers 'e'
{Y*12+(X/8)+L6} e X^8


If you already had the location of the buffer's byte, I would say yes (like from scanning a horizontal line of the screen).  But if you have to find it given just an X and a Y, the extra math to find the particular byte and bit from the buffer is going be less optimized than if you just used the pxl-test command since it does all that math for you but in optimized assembly.

Nice to see ElseIf and Else!If; that should help reduce some excess End's in programs.
Keep up the good work!

The only way to get less flickery gray is to update the screen more often. If you're doing things like drawing sprites, a good way to help maximize the update frequency is to make sure you're only drawing things on the screen that moved or weren't there before and actually need to be redrawn. Also, optimize your program for speed as much as you can. Use as little processing power as you can between screen updates, and try to make sure the time between updates is somewhat constant and doesn't have large spikes of processing time used up between two screen updates.

If you wondering why there's no automated process to display grayscale without having to call DispGraph^r/DispGraph^rr, it's because that would require interrupts to update the screen automatically, but the display routines don't work with interrupts. You wouldn't want that anyways, because it would display the buffer contents a potentially inopportune moments, which could cause tearing (the screen updating while the buffers are being updated, resulting in displaying part of the new image and part of the old).