... which should be done in the code displaying
the battery gauge -- i.e. the application level --
not the OS API level.
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi/sec: not just a good idea, it's the LAW!
[EMAIL PROTECTED] wrote in message <5103@palm-dev-forum>...
>
>
>
>Actually, the real reason is that when batteries sit on the shelf for a
long
>time, the voltage is reduced somewhat. I don't know if it makes any
difference
>to the life of the battery (if it does, its probably very slight), but this
>difference was enough to make our battery gauge appear not-quite-full.
User's
>wouldn't appreciate that, so batteries that are almost-but-not-quite full
are
>rounded up to 100%.
>
>HTH...
>Jesse
>
>Alan Pinstein wrote in message <5090@palm-dev-forum>...
>>
>>'zen of palm' as far as I can tell... apparently if the batteries are that
>full (ie, 90% plus) then the user has no need to know more resolution of
the
>battery level besides 'FULL'. In my opinion that type of behavior should be
>done at the application level.
>>
>>Alan
>>
>>>Why would they do that??
>>>
>>>-rmh
>>>
>>>
>>>
>>>Alan Pinstein wrote in message <5046@palm-dev-forum>...
>>>>
>>>>Hey, I know the answer to this one! For some reason, Palm decided to
>alter
>>>the % range of this function according to this algorithm:
>>>>
>>>>percentage = truePercentage;
>>>>if (percentage >= 90%)
>>>> percentage = 100%;
>
>
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
