I usually do both. First, I check for the features I need, regardless of which device it is. This tells me if it's possible to perform the task necessary. Second, I'll check the device against a list of devices I've tested. If I haven't tested the app on that device, I'll often put up a one-time warning dialog.
On 5/4/07, Douglas Handy <[EMAIL PROTECTED]> wrote:
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 -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
-- [Jeff Loucks] -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
