> 1. When you creating a new project in CodeWarrior you have to choose
> between following
> a. Palm OS 3.1(English) Stationary
> b. Palm OS 3.5 Stationary
> Hence CodeWarrior will generate machine code targeting
> either 3.5 or 3.1 version, but not both!
you can use 3.5 SDK and your application will run on 3.1 as long
as you dont use any API's that were not in 3.1
> 2. Beside different compiler setting Palm OS 3.5 handling forms
> differently. If you use standard
> code to handle forms it will crash 3.5 debug rom. At the
> same time if you target Palm OS 3.5 -
> prior versions will not function properly.
really? i use the same code
> 3. Palm OS 3.5 handle writing on the screen different than 3.1. If you
> use standard approach which works for versions
> 3.0-3.3 you will crash 3.5 debug ROM.
if (palmos3.5)
do_xxx;
else
do_yyy;
where is the problem?
> 4. Palm OS 3.5 using improved functionality for Bitmaps. But these new
> functions are not recognized
> by versions 3.1-3.3, they simply crash. If you use old
> approach to bitmaps it gives errors in Palm 3.5.
thats because the API didn't exist in the earlier roms.. its like
telling windows 3.1 to handle NTFS :) if you want to support it,
you will have to write your own library and work around the
problems..
all us developers (especially gamers) have been banging our heads
against the wall with these issues - but, we solve em.
// 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/
