Quote:As far as typos go, yes the _RED is different from _RED32 but is there a difference between them?
There's one real difference in the two: RED32 *always* returns a color value from a 32-bit color value, whereas RED returns a color value based on the current screen _DEST (or _SOURCE, whichever it's based on...)
For example, give this a run:
In Screen 0, 4 is red. For a 32-bit color, 4 is &H00000004... no alpha, no red, no green, and 4 blue... It's almost completely transparent black!
So WHY do we have two different RED commands?
_RED is flexible and returns red values for EVERY screen mode --- but that makes it relatively slooow.
_RED32 *only* works for 32-bit color values --- but it's much, much, much faster!
As long as you're in a 32-bit screen, you should *ALWAYS* use _RGB32, _RED32, _GREEN32, _BLUE32, _ALPHA32. It'll speed up your program considerably.
If you're in SCREEN 0, 12, 13, or a _NEWIMAGE(x, y, 256), then use _RGB, _RED, _GREEN, _BLUE, _ALPHA. Otherwise, you're not going to get the results you want. It's slower than _command32, but it tells the program to use the existing color palette with the color value you specify and only then return the proper result back to you.