If you look at the commented version it would probably make a lot more sense. Also, you would know that "DG" stands for DispGraph. Any time the screen needs to be updated while sprite editing, I call this, which will perform either DispGraph, DispGraphʳ, or DispGraphʳʳ according to the sprite's grayscale level.

** Anyone who wants to, feel free to look at the source code and suggest optimizations. A good place to start may be areas that are easier to understand without knowing the intricate structures of the specific program, namely routines that perform math/graphics operations. Rotate and flip could be good candidates for this... It's really hard for me to add features with the current features already maxing out the program's size! **

I'm just checking, because I thought somebody said this a while ago... can a program archive itself at the beginning of execution? And if so, what's a good way to make sure it exits in the same status as it began? With a variable?

Hey that is really cool!  Definitely will consider adding this to the Axe Tools, with your permission of course.

Sure, although it's still a work in progress. Should I start a new thread for it? Or just keep updating my post on the second page?

Ok, just tested it and the fix is working.
Here's the edited source and the Axe executable.

Beat you to it

But sorry about that, I was testing it on a 6MHz and I forgot that I needed to turn off Full for the grayscale. And can you or somebody else with a 15MHz test my updated file just to make sure my fix works?

EDIT: Found another dumb error and fixed it.

EDIT AGAIN: Found another dumb error caused by my previous fix for a dumb error and fixed it.

That's a lotta comments... Of course, it's probably unreadable now.

Yeah, the program is so large I need the comments or I won't even know what my code is if I leave it alone for over an hour. Although I think most of the size bloating is from indenting 2 spaces per layer every line.

A reminder:

** If you find any glitches, want to make any suggestions, or just want to tell me how great of a guy I am for making this, tell me about it! **

Yeah, it's a really big program... If you want I can probably post a much smaller version of the source, with all comments and indentation removed

Hit PRGM to scroll to the error, what is it citing as the error?

It would be nice to include some better sprite management features like copying, but with the compiled program pushing 8 KB as it is, it will be difficult to add this. But those are finishing touches sort of features, so until I even figure out how to fit those into the program... I present the awesome features!

-8x8 or 16x16
-Black and white, 3-scale grayscale, or 4-scale grayscale
-Multiple zoom views visible at once
-Realtime sprite hex display
-Hex input
-Flipping horizontally or veritcally
-Rotating clockwise or counterclockwise
-Create, edit, and save as many sprites as memory allows
-Delete sprites

Go ahead, try it out. I attached the source and compiled versions, as well as a readme to explain how the hell to use it. If you plan on compiling the source on your calculator and don't want to use the 14,082 byte commented and indented source file, download the attached uncommented and unindented version, weighing in at only 5,714 bytes!

** If you find any glitches, want to make any suggestions, or just want to tell me how great of a guy I am for making this, tell me about it! **

** Anyone who wants to, feel free to look at the source code and suggest optimizations. A good place to start may be areas that are easier to understand without knowing the intricate structures of the specific program, namely routines that perform math/graphics operations. Rotate and flip could be good candidates for this... It's really hard for me to add features with the current features already maxing out the program's size! **