The code I'm using is... WinHandle winH; BitmapType *bmp; UInt8 version; UInt32 attr;
winH = WinGetDrawWindow(); bmp = WinGetBitmap(winH); version = BmpGetVersion(bmp); attr = ((BitmapTypeV3 *) bmp)->pixelFormat; 'version' is the same (== 3) in both the cases. And so is the pixel format (== pixelFormatIndexed). When run on a simulator, the colors of the shrunk bitmap are distorted in a sense. On processing this same bitmap through the same code for the second time, the colors seem to be restored, although not entirely. One of the Treos concurs with the simulator. The other, however, works as expected and produces a distortion free image. >probably endianness issues. try byteswapping all the samples if the >image is 16bpp On 5/3/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > My code fetches the screen bitmap, shrinks it to one-fourth its original size > and displays the new bitmap. The same code, when run on two Treo 650s, > displays the bitmap quite differently. There's a color discrepancy. I checked > the screen depth, bitmap depth and all the other parameters that could cause > it, with no avail. Has it got to do with the hardware? > -- -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
