Hi!
> This is a timing problem. If you take too long to pass a vchrLowBattery to
> lost or something.) So you mustn't put in a big delay, but rather hand it
> along to the system as soon as you can.
>
> I think I also remember that vchrLowBattery might be sent even when the
> battery isn't low, that it was used as a signal to a different part of the
> system to check the battery, but I could be mistaken.
>
I think its rather the latter. I do not have a big delay. My pause() method that I
mentioned as a reaction to the vchrLowBattery
only sets a flag variable, so essentially my code is:
do
{
get event(wait forever if paused, only a short time otherwise)
if (lowbattery)
{
set pause flag
}
SysHandleEvent(event)
}
while(not appstop)
So I guess the system is rather sending events to itself for internal purposes. This
would also explain why the low battery warning
dialog never shows up...
Cheers,
Tilo
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
