On Mon, Aug 04, 2003 at 10:45:13AM -0400, Alexander R. Pruss wrote: > I've run into a theoretical snag with my rotation support. I assume that > bitmaps store data in big-endian order when I rotate the bitmaps. This is > true for OS 1-4, and is true for my NX, but there could be some units, > perhaps now and perhaps in the future, that will store bits in little-endian > order in V3 bitmaps created by BmpCreateTypeV3().
That's a question to ask palmsource :) > I have a few options: > > 1. Do nothing and wait to see if anybody complains about rotation producing > scrambled text/images on an OS 5+ machine. This is not a dangerous option, > because given how the rotation works, scrambled text/images in rotated mode > is the only bad thing that would happen. It wouldn't crash or anything like > that. (Note, too, that if anybody reported a problem, I could cobble > together a solution on a moment's notice but at the cost of higher memory > consumption. This would involve using 8- or 16-bit bitmaps instead of 1-bit > for text rotation.) That would be best. Palmsource does a very good job IMO of maintaining downward compatibility (with the exception of hacks in OS5) so I would guess that it will remain the same. -- Adam McDaniel Array.org Calgary, AB, Canada _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
