From: "Gert van Kruiningen" <[EMAIL PROTECTED]> > Events are sent by the "serial read function" to the active > window to inform it about certain data that has arrived and (snip) > My problem is that sometimes, the event queue overflows. > The Palm OS event queue is quite shallow, fine for the purpose it was designed for, but not for heavy use of custom events for notifying background activity. You should also be aware that any Palm OS dialog (keyboard, alert, etc) will consume custom events, breaking your communication between the background process and the interface.
I've found it far better to either use a different notification mechanism (write the data to a database and display to the screen from the database, deleting the records as they're displayed?) or to build your own event handler. It's really not that much code - a fixed array, a function to add events and a function to check for events. You can re-use the Palm ] OS event structures for simplicity or define your own structures. Although it's a chunk of work, you walk away from a number of problems associated with the Palm OS event handler and background processes. Chris Tutty -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
