I’ve removed the polling and substituted a notification hook on the ‘hede’ event. I don’t even know what that is but I know that it’s to do with input events and it slows down your device to have apps hooking it. I’m only hooking it when the LED is on though. If you leave off the LED checkbox the ‘hede’ event won’t get hooked. The only time you should notice any impact is if you ignore pending alerts.
I’ve got the AlarmTriggered events purging the followup AlarmDisplay events but the delay caused by turning the vibrate on and off means the screen still wakes up. Worse, it seems the device completely wakes up before the AlarmTriggered is delivered so I can’t even set a flag to force the device back to sleep.
Update 28 February 2008
I found this while grepping through my PalmOS headers.
#define sysNotifyEventDequeuedEvent 'hede'
This ominous sounding comment accompanied it.
Sent for each event being returned by EvtGetEvent. Be very about registering for this; you can easily impact performance (in a bad way!) Also note: for speed, notifyDetailsP points to a event structure with system-native endianness, meaning you might need to byte-swap what you read depending on what endianness your code uses. Note: future OS releases might not send this notification.
