>but apparantly gDeviceP was a field in a structure that
>>has, for some reason, vanished in the latest versions of the OS. I
>>asked this question, got no replies...after I had done a search through
>>every reference I could find, including many of the Palm headers.
>
>Err...the field vanished. The structure it was in is still there I
>think. And as Aaron said, it's probably because it was kind of hackish,
>by trying to grab bits directly from the hardware level. This would
>have made it horrifically incompatible with some of the new hardware
>coming down the pipe.
Precisely! And if I may quote from that very sample:
/*
Now, this is the tricky part. There is no API for getting the bits on
the screen into a bitmap, so this code is unsupported and will only
work on Palm OS 2.x, 3.0, 3.1, and 3.2 devices. This is why we limit
this sample to only those versions in the RomVersionCompatible
function. This code will also only work on a device with a screen
depth of 1.
WARNING: THIS CODE IS NOT SUPPORTED CODE AND MAY NOT WORK ON DEVICES
WHOSE OS VERSION IS OTHER THAN 2.X, 3.0, 3.1, OR 3.2
*/
On 3.5 and higher, you've got some beautiful APIs to use, and they're even
in the documentation (hint hint). Prior, you have to hack, and this is
showing you how to hack. But I'm not sure how to say it more clearly than
the source itself, that it won't work on 3.5 and higher...
(Or I don't know what's on RoadCoders - possibly they've cached old
versions of our samples? Hopefully not. See our KB for our latest samples,
if you've got old ones.)
-David Fedor
Palm Developer Support
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
