Our application works with the Calendar database directly adding, updating, and deleting items. We have found a problem that we have not been able to find a solution for.
The problem is when a Calendar item is added that contains an alarm that SHOULD be the next Calendar alarm to be displayed. This is most easily reproduced when there are no calendar items and one is added with an alarm. Because the native Calendar application is responsible for setting alarms and it has no knowledge of our application adding a new item, the Calendar application does not recalculate the next alarm and reset the alarm with the alarm manager. This means new item's alarm never expires. Is there a way to force the Calendar application to recalculate the alarm? I'm assuming the Calendar application will calculate the next alarm to expire and then set that to the alarm manager. When it expires, recalculate again and set the next to expire again. I know there are certain system events that trigger the Calendar to recalculate the alarms (like hotsync and soft reset) but we obviously do not want to do this every time we add a calendar item with an alarm. Is there a better solution? -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
