I understand Alarms... (I think, and have used them before 'back in the day') but only in a single db, single alarm scenario.
Your app can install but one alarm at a time, and it's up to you to handle/manage alarms if you want to support more than one (ala the Datebook application and it's myriad of routines designed to support this). I have a need to support alarms for an application that can have multiple databases, and each database may have it's own collection of alarms. Some of these database may contain 1000's of records, and they need to be kept in order as they are and can't be 'optimized' based upon alarm times. I'm assuming it's best/most efficient to manage these alarms out of one common alarm database right? This brings about mucho code changes, as if any of those database go missing, renamed, etc, the alarm database will also have to be maintained/updated. While not a monumental task, it sure doesn't sound like much fun :) Anyone else have a better way to approach this? -MD -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
