Jim Schram,
Thanks for your quick reply,
On Sun, 5 Mar 2000 20:56:38 -0800, you said:
> unless of course you've taken specific measures to ensure
> that the proc pointer does remain valid. There are several
> ways to accomplish this
I am pleased to hear that it is possible to make the pointer stable.
Can I ask you to elaborate on this or could you please point me to a
place where I could read more on how to accomplish this?
> but the obvious question is why not use a launch code based
> alarm if it's expected to go off after your application has quit?
There are two reasons: one is critical one is just annoying. First, I
need to avoid lighting the display every time this alarm triggers. The
first time I tried this program I killed my batteries in 36 hours. I
can reduced the auto off to a smaller value but eventually it would be a
pain to use in other applications for obvious reasons. Second, waking
the display is a pain if the device happens to be in my pocket since it
doesn't shut off ever in that circumstance. There is probably a hack
to help with the second problem but there is the power consumption
reason.
There is no user input required for this activity. Why wake the display
and the com port and all that jazz when I don't need to.
Is there some way to ensure the validity of my pointer so that I can use
the Procedure Alarm?
derik
email: [EMAIL PROTECTED]
WWW: http://www.pobox.com/~derik
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
