There are two ways to avoid a crash like this. One is to check the version of the OS
you are running on and if it is less than the
supported version, pop up an error message and exit out of the app. The second is to
disable features selectively that use new OS
calls if you desire to run on an older OS. I all considered your market and whom you
are selling to. I find it a mustto support at
least back to 3.1 if you have any horizontal application out there. If your app has
some really cool wiz-bang functionality that
would need 3.5, then just support that.
Steve
Manal Milad wrote:
> Another question:
> I was using SDK 3.0 and then I switched to 3.5, because I am buying Code
> Warrior 7 and I want the migration to be smooth.
> Now, to move to 3.5, I had something changed like the types and so on and
> this is perfect now. I can compile without any problems.
> My question is:
> What if I am using a function that is supported in 3.5 on a 3.0, 3.1 ROM
> version? What will happen? Would I get an error? If so, is there a specific
> error that pops up in such cases, so I can know that this is my problem, so
> that I don't waste my time trying to figure out what the error is when it is
> only that the ROM version does not support this function?
>
> Thanks again
> Manal
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe, please see
>http://www.palmos.com/dev/tech/support/forums/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
