My app has to do some screen ajustments to let system popups pass thru. So i look for keyDown events with chrCode like alarmChr to switch into safe mode and let system draw what it wants. OK, that workes fine, the user after looking at alarms and likes has an opportunity to press button and resume Then I notice, that "batterry low" warning stuck. Never mind, I add lowBatteryChr into consideration, and again, my app switches into safe mode, my start form and system warning above it both appeares, and after pondering where i can get batteries at 3 a.m. i can return to work. That's all right - my batteries are drained. I have replaced them, do my app testing, and in regular periods - my start form and no any warnings!!! What a loss. Why system sends lowBatteryChr when it really has not to? Batteries are OK, no warning will follow. What can I do with that? Help, please. Thanks, Eugen P.
