> Just to check: you do realize that directly accessing the screen and its
> internal data structures is not guaranteed to work in future OS versions,
> right?
:)) i realize :) and as a result, i only use direct access like that
on known CPU types (where i know the endian is correct).. else? use
API :P adding the CPU check was a result of running on that ARM
prototype board at PalmSource 2000 :)
Cube3D is a perfect example of knowing when to choose - but, like david
said.. do so at your own risk :) be expected to make an update in the
near future if a new device comes out and your code no longer works..
if you are not prepared to make adjustments when needed - stay away
from the area.. there is nothing worse than an app developed for
2.0 that doesn't run on 3.5 and the developer has gone bye-bye
// az
[EMAIL PROTECTED]
http://www.ardiri.com/ <--- free games!
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
