Okay, fixed that and a couple other bugs caused by the same problem.

This has to be one of my dumbest bugs ever... One single mistake with order of operations was corrupting every exported file with a byte $0D (which happens to be required in the new 8X* format)

I've noticed that there is no way to copy a sprite, or shift it.

* shmibs was confused about copying as well, but you can do it. copy the value from the text box below the sprite, click on one for a different sprite, and hit ctrl+v

Okay, I just changed that. You don't have to highlight the text box to copy anymore—just press Ctrl+C from anywhere.

shifting would be nice, though.

Yes it would. I'll work on that as soon as I find an appropriate character to represent it in the control panel.

EDIT: More updates!

Update

New:

• Shift (really more of a rotation, but "rotate" already means something else) your sprite left, right, up, and down
• All items in the control panel now have keyboard shortcuts

Changed:

• Ctrl+C no longer requires you to highlight the sprite hex data first
• Control panel icons are smaller in order to make everything fit - hope you don't mind

Fixed:

• Remnants of the bug corrupting exported variables should be entirely fixed

Request: have tilemaps size variable, so that when we have 5*5 sprites there is not 3 pixels around them in each direction. (or am I just stupid and this is already available?)

Update

You can now export your tilemap as an image! GIF, JPG, and PNG files are supported.

Mostly because I found myself constantly exporting as a Pic only to upload it to SourceCoder to get the GIF (which was black-and-white and too small for my taste).

cool =D
this will be really useful for people trying to keep track of large maps (or who want to add documentation/walkthroughs to their games)

That looks useful, especially for people who want to import maps from other games.

But you should really finish greyscale tile support first

I might consider extending it to support any size sprite between 2x2 and 16x16, but that will involve rewriting most of the code. (Rotation would also be significantly more complicated with odd-numbered dimensions )

The addition of variable sprite sizes would be an incredibly useful feature. Rotation wouldn't be any more difficult, either. Rotation of an n x n matrix is done the same way for both even and odd values of n. You wouldn't need to have separate routines or anything...

As for importing tilemaps, I'd say that variable sprite sizes would be more useful than importing tilemaps, but even so I agree that just because imported maps would be limited to 8x8, it wouldn't mean the whole application would need to be limited to 8x8.