>One strange thing here. Video memory address is determined via processor used,
>but all I found is that PalmIIIc has faster processor.
That isn't actually true in this case. The Palm IIIc device has a separate
chip doing the screen management; it isn't the EZ doing the work.
>Are you sure that it is
>actually Motorolla 68328EZ (sorry if mistype) as in previous Palm? If yes, how
>could you explain the return of NULL from it's hardware register
>(0xFA00)defining video address.
Yes, it has an EZ processor. But the EZ's hardware register setting in
this situation is irrelevant and unused. Which is the whole reason that we
give APIs for you to use, like WinGetBitmap and BmpGetBits: so that you
don't need to make assumptions like these about the processor or other
hardware details!
There are some times where there isn't an API, for example WinGetPixel
doesn't exist before 3.5. In those cases, if you're on an old system, you
have a reasonable degree of confidence in making assumptions and directly
accessing information, because the device characteristics are well-known
and people can't change the past. (Of course a licensee could come out
with a new device running an old OS, though.)
But on 3.5+, where there's an API, you'd better use it because the hardware
can and will change in the future.
As for newer docs: the 3.5 SDK has does dated from early January, which are
reasonable. One of the docs folks is checking for me as to when a newer
cut will be done. The writers write continually, but doing a publishable
release only happens every so often.
-David Fedor
Palm Developer Support
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
