Normally, I'd agree, but today I am alone and being argumentative 8^).
I would prefer not to have to rely on someone else's program responding to
launch codes consistently (especially between versions). The Alarm Manager
routines are there for a reason, they should be used. The amount of code
duplication is negligible ...
Scott's original code will have code to update the Datebook db (no change in
code size there), and everything else is an if test wrapped around two API
calls and maybe some data declarations. Not exactly high overhead code
there. If it is this easy, it should just be done in the code ...
Regards,
CSE
> On Behalf Of Robert McKenzie
>
> This is my option #2.
> But I certainly side with Peter (my option #1), let datebook do it.
> Why clog up the palm with duplicate code if you don't need to???
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/