I now realize that (of course) you are correct.... and I can hit the database and
extract the information I need..... but I'm worried about spending too much time
performing these actions in response to a sysAppLaunchCmdAlarmTriggered
launch code. According to the documentation, one should not perform any
significant (time-consuming) tasks at this point since the OS has to inform all
installed apps. In order to determine the next alarm time I need to read and compare
records from several DBs and do some processing.
I guess I COULD do all this in response to the sysAppLaunchCmdDisplayAlarm
instead..... OR pre compute the alarm times and store them in a separate DB....
What do you think?
Thanks Again!
Dan
"Eric W. Sirko" wrote:
> > In order to determine the next alarm, I need to access information that is
> > normally kept in global variables, but I (of course have no access).
>
> Global variables do not survive the termination of your application, so how
> would you "keep" any information there? Normally, we use the Database
> Manager for saving information across program invocations. Note that the
> alarm mechanism provides a way for your app to get control when it is not
> the current app.
>
> Hope this helps...
>
> Eric W. Sirko
> Softworks Solutions
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
