Hmmm... I'd use a shared library to store the events, and I'd setup the library to handle a custom notification that tells it to read the queue and store it. You can send custom notifications at interrupt time using SysNotifyBroadcastFromInterrupt. This is only available on Palm OS 4 and later, but that may be an acceptable requirement if you're building custom systems and can control the hardware used.As soon as I receive the event I want to put it in to an event database. I read on the palm website that you should not write to data storage memory while in an interrupt handler. Instead it recommends that I create a custom event and post it to the event queue. I don't want to do this because if the user has the keyboard open, or some other system dialog, it will toss my custom event away and I will never get it. I cannot miss these events. That is why I want to write it directly to an event database and then exit. Is this feasible? The only other thing that I might do in the interrupt handler is put a custom event in to the event queue that says what type of event I received just incase the form that the user is on needs to report the event (this event is not important if the keyboard is open).
--
Ben Combee <[EMAIL PROTECTED]>
CodeWarrior for Palm OS technical lead
Palm OS programming help @ www.palmoswerks.com
--
For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
