At 5:53 AM -0700 1999/04/19, [EMAIL PROTECTED] wrote:
>If I understand what your saying, I can provide an "interrupt handler" to do
>some work even though my application is not running. By placing it in a
>shared library, the system will have access to the routine at all times.
Yes, but to be specific, only as long as your shared library is SysLibLoad-ed.
>Would I be able to send a "Launch Code" to my app from the interrupt?
Unfortunately, no. Sending a launch code requires memory allocations, which are not
interrupt-safe. The only event routine which is safe to call at interrupt time is
EvtEnqueueKey. How you'll integrate the two may be... rather difficult.
Regards,
Jim Schram
3Com/Palm Computing
Partner Engineering
