Hi All, This is my first post, and I've searched the archives for an answer but found nothing specific, so forgive me if it has been covered before. I have an application that polls the serial port periodically (say every 10 seconds), I do this by setting an alarm (AlmSetAlarm) and responding to the subsequent sysAppLaunchCmdAlarmTriggered launch code. I am setting the purgeAlarm to true after I've done what I need to do so that I don't get the sysAppLaunchCmdDisplayAlarm. This is all working fine, and I'm getting the data I want without the user knowing that it's running in the background whilst they are using other applications. Here's the problem; once my application responds to it's alarm, the Palm won't turn itself off, it seems that every time an alarm is triggered the auto off timer starts counting from zero again and never reaches the auto off after x seconds. The only way I can see to get around this is to write the auto off timer functionality into my code, this will mean that I have to know if any user interaction is taking place at any time otherwise I would be turning the Palm off after my preset time whilst the user may be writing a memo etc., presumably I would have to hook into the sysNotifyEventDequeuedEvent notifier to get this - Palm says this degrades system performance. So... Is there any way of making the Palm "ignore me" so that it does not reset the auto off time, or at least be able to read how long it is to the auto off time and adjust this value accordingly. I assumed that by setting purgeAlarm to true that nothing would get upset. Can anybody think of a better approach than what I've come up with? Regards John Sutton
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
