"Douglas Handy" <> wrote in message news:[EMAIL PROTECTED] > David, > >>Does anyone have suggestions? > > As others have mentioned, some current Treos already don't use 'hspr' for > the > company ID. I also use a simple IsTreo() function which I update as new > devices > are known. > > But what arguably is a better idea is to check for the existance of the > feature(s) you care about. That is, instead of trying to decide if it is > a Treo > per se, if what you want access to are portions of the phone library then > check > if that library exists instead of whether the device is a Treo. > > That not only future proofs against not correctly detecting a future > device is a > Treo, but means that if a future Treo doesn't have a compatible phone > library > that you won't try to make calls to it. > > But again, it may depend on why you care if it is a Treo... > > Doug
Hi Doug, and thanks to the rest for their input as well. Yes, I normally do the above also, but was looking for "a better way". The whole point of this particular exercise was to know when to call the HsGetVersionString API to get the Treo's ROM serial number, because some Treo designer somewhere sometime decided that it would be too easy for developers just to keep it available via the standard SysGetROMToken API... I can't use SysGlueTrapExists(HsGetVersionString) because HsGetVersionString isn't a regular trap API, but rather a SysTrapOEMDispatch selector based API... Oh well, I'll just keep doing the specific device model checks and update it again when the next model comes out. Regards, -- David Thacker http://www.SatelliteForms.net The Premier RAD Tool for PalmOS & PocketPC -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
