Neil, Bummer!
Thanks for the CompanyID tip. I tested on real 600 & 650 devices, but only tried against the 680 and 700p sims, which do report 'hspr' as the CompanyID. I should have checked Hal Mueller's list also. I already do have an IsTreo function that checks the known sysFtrNumOEMDeviceIDs, but was trying to find a way to do this without having to update that routine for each new PalmOS Treo. I guess I'll just keep doing it that way -- it's not like Palm is bringing out a new Treo model every month... Regards, -- David Thacker http://www.SatelliteForms.net The Premier RAD Tool for PalmOS & PocketPC "Neil Whitworth" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Not all treos use sysFtrNumOEMCompanyID == 'hspr' > > device sysFtrNumOEMCompanyID / sysFtrNumOEMDeviceID > 600 'hspr'/'H101' > 650 'hspr'/'H102' > 680 'Palm'/'D053' > 700p 'Palm'/'D052' > > There is no simple way of future proofing your code. We have a simple > IsTreo function that is used throughout our code to detect if it is a treo > device, and we have to update this each ime a new device comes out. But at > least it is just one small change. > > David Thacker wrote: >> Hi all, >> >> I want to detect if the current device is a PalmOS 5.x Treo. I know I >> can check the sysFtrNumOEMDeviceID and compare against known Treos, and >> that is what I have been doing to this point, but I'd rather use a >> detection scheme that can detect both current and future PalmOS Treos. I >> don't care about pre-PalmOS 5.x Treos. >> >> Let's say, for example, Palm decides to bring out a new PalmOS Treo, say >> maybe a Treo 755p. I want my code to be able to recognize that device as >> a Treo without having to be updated with the future sysFtrNumOEMDeviceID. >> >> Does anyone have suggestions? >> >> I was thinking that since all of the existing Treos use the >> sysFtrNumOEMCompanyID of 'hspr' (Handspring), that I could just check for >> that CompanyID and a PalmOS version of 5.0+, and that would indicate a >> Treo. However, I'm not sure future PalmOS Treos will still use that >> CompanyID... >> >> Does anyone have any better suggestions? >> >> Or, does anyone at least know if a possible future PalmOS Treo will still >> use the 'hspr' CompanyID? >> >> Thanks, >> >> 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/
