If I may make a modest request of you good folk

Since my app will NOT support v 3.5  how can
this function be re-written to handle such a case...

as in to test if  I'm on a minimum & not 3.5 or above

My first thought is to toss both a min & a max version
if (romVersion < minVersion)
if (romVersion > maxVersion)

Am I heading in the right direction here?

in the past I've defined my version like so....
#define Version sysMakeROMVersion(2,0,0,sysROMStageRelease,0)

but I actually stopped using this function and I guess
I should re-incorporate it to test for too HIGH
a rom revision.....

I hope this will make a useful contribution
for those who need to test for COLOR or
monochrome devices as well

(but I am not in the know as to how they currently
 gather this information & display color)

******************
>From the CW stationary......

static Err RomVersionCompatible(DWord requiredVersion, Word launchFlags)
{
 DWord romVersion;

 // See if we're on in minimum required version of the ROM or later.
 FtrGet(sysFtrCreator, sysFtrNumROMVersion, &romVersion);
 if (romVersion < requiredVersion)
  {
  if ((launchFlags & (sysAppLaunchFlagNewGlobals | sysAppLaunchFlagUIApp))
==
   (sysAppLaunchFlagNewGlobals | sysAppLaunchFlagUIApp))
   {
   FrmAlert (RomIncompatibleAlert);
     // Pilot 1.0 will continuously relaunch this app unless we switch to
   // another safe one.
   if (romVersion < sysMakeROMVersion(2,0,0,sysROMStageRelease,0))
    AppLaunchWithCommand(sysFileCDefaultApp, sysAppLaunchCmdNormalLaunch,
NULL);
   }
    return (sysErrRomIncompatible);
  }
 return (0);
}

******************



-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palm.com/devzone/mailinglists.html

Reply via email to