The problem with one-bit stuff is getting that bit out of there. You have to break apart a byte to get at each bit and it's a hassle with code. It keeps the image size down, sure, but it's not fast.
You'd be much better off going with 256-color images. Still enough color to do most artwork, animates fast (one-byte per pixel, easy to calculate offsets), and small in size.
Other than that, 32-bit would be fastest from the point of view of accessing (quickest to access a 32-bit offset) but it's a pig when it comes to space.
- Tab
At 02:02 PM 9/12/03, [EMAIL PROTECTED] wrote:
> On a different, but related note, try using 1-bit members versus 32-bit. > 1-bit will animate slower than 32-bit, even though it is 32 times as small.
Really? I've been using 1-bit bitmaps for my text highlighter, with the belief
that I can resize and reposition them more quickly and reliably than a bitmap
with more color depth. Have I been deluding myself? Performance has been an
issue, but I figured it was just because there was so much Lingo.
Cordially,
Kerry Thompson
[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
