Ben Combee <[EMAIL PROTECTED]> wrote: > At 08:36 PM 5/14/2004, you wrote: [...] > Also, on event-driven systems, not all events are for your program. > Palm OS sends a number of events that just pass through the event > loop briefly before getting used by SysHandleEvent -- this is done to > give applications a chance to intercept those (a way of extending the > system), as well as a way to have parts of the OS not have to know > where event come from -- they get posted to a queue, and at some > future time, the OS pulls them out of a queue. > It would likely be useful to know which services are fed by the event loop. I presume they include: any screen taps etc, button presses and IrDA. Those that are not, I guess TCP/IP, alarms, receiving (and sending from buffer etc) serial data, the reset button etc etc...
Or is there good information on this somewhere that I've missed. I have, for instance, looked for details on how networking and IrDA are driven and what conditions for working they have. As an arbitrary example I presume that if the application is in a blocking TCP send/recv call then IrDA will stop. -- Alan J. McFarlane http://homepage.ntlworld.com/alanjmcf/ Please follow-up in the newsgroup for the benefit of all. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
