>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
Actually, I got my original sample right off the KB.
Note: Since then, the link to the old one had been broken. I
downloaded it about 4 weeks ago, I don't know if it's still lingering
on somewhere on the server. I wasn't aware that there were new
examples of this, though...I'll need to check that out.
As an aside, I was used it on a Symbol SPT 1700, with the 1 bit
screen depth and running 3.2. (Just to see how it works...the
signature++ example has some good examples of how to use the older
API's, though, as well as a conduit for syncing bitmaps. If nothing
else, it's still kind of useful for that.)
-Rus
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
