I suspect one or more comm stack (or other driver) is needing to poll. EvtWakeup() can be called by anything and will wake up the foreground. If there are no real events, EvtGetEvent() will return a nilEvent. EvtSetNullEventTick() can be called by anything to set the minimum ticks until an EvtWakeup() occurs. Libraries, extensions and drivers will use these calls to wake the foreground as necessary to keep the OS alive. Remember, almost everything happens in either EvtGetEvent() or in the event handlers immediately following.
-------------------- Jeff Loucks Work 425-284-1128 [EMAIL PROTECTED] Home 253-851-8908 [EMAIL PROTECTED] Mobile 253-691-8812 -----Original Message----- From: Gert van Kruiningen [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 15, 2005 7:19 PM To: Palm Developer Forum Subject: RE: EvtGetEvent on T3 You are right Jeff, With the timeout set to -1, this simulator just goes to sleep because there is nothing to process, and if you move the stylus over the screen, it starts to move again. But on the real T3, it keeps on racing along. So the trick is to find out what the events are that it comes back with. There is no such thing as "View" "Events" on the real T3, but displaying data on the screen, events coming out of EvtGetEvent() does not seem to work yet!!! Oh its going now and guess what, it's the nilEvent that is returned all the time by EvtGetEvent(), until you move the stylus on the screen of course and press buttons. Where is this nilEvent coming from? Anybody got an idea? Gert -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
