All of this talk about writing directly to the screen makes it seem like somewhere in our code we have some variable set to writting to location $1f000000. But the way I access the screen is through a genuine Palm OS API: pucScreen = BmpGetBits(WinGetBitmap(WinGetDisplayWindow())); And as people say, I can freely check if, say, 8-bit / 160 x 160 mode is available, and through the DisplayWindow Bitmap, I can even tell if the pitch (rowBytes) is nolonger 160. If, in the future, completely radical changes are made to the Palm Desktop (such as movable overlapping windows or using hardware acceleration for screen operations). The PalmOS could easily hook and emulate this call by giving me access to a 160 x 160 bitmap that is then periodically updated to the real screen inside my own application's window. (A future Palm is likely to havemore memory and speed to emulate the old Palms anyway.) So I guess my question is - by saying that "writing to the screen" is illegal, is Palm now saying that BmpGetBits is illegal or WinGetDisplayWindow is illegal? Why shouldn't this legal API call work on any Palm? (Yes, I could not check screen info correctly - I might write to a bad address - but I might do that on any line of my code in any context, not just on screen access.) -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
