According to the documentation, one cannot access global variables during
a launch with sysAppLaunchCmdAlarmTriggered. I *thought* I understood
what this means but now I'm not so sure.
If one is really restricted to the (automatic) variables in the function that is
called by
the OS in response to this launch code, then it seems to me that VERY little
processing could be done! I know you also have access to the the caller-defined
value specified when the alarm was set with AlmSetAlarm .... but doesn't seem
to help all that much!
It looks like all you could do is say :
If this type of alarm went off.... set another type in X seconds (where the X could
not depend on .... well anything the program is doing!)
I've read that Mr. Ardiri performs a cute trick to get around this... and I plan to
look into it.... I'm just trying to verify that I understand the situation. I would
think
that I would see MANY more posts on this topic I am correct!
Thanks,
Dan
(email appreciated [EMAIL PROTECTED])
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
