Palm OS Programming Bible 2nd Edition, p. 89, says "Most applications should pass the constant evtWaitForever (equal to -1) as the second parameter of EvtGetEvent. The evtWaitForever constant tells EvtGetEvent to put the system into doze mode to conserve power until another event enters the queue."
This seems to imply the latter.
The PalmOS Programmers Companion, chapter 10, says:
"Normally, applications don't need to be aware of power management except for a few simple guidelines. When an application callsEvtGetEvent to ask the system for the next event to process, the system automatically puts itself into doze mode until there is an event to process. As long as an application uses EvtGetEvent, power management occurs automatically. If there has been no user input for the amount of time determined by the current setting of the auto-off preference, the system automatically enters sleep mode without intervention from the application."
"Applications should avoid providing their own delay loops. Instead, they should use SysTaskDelay, which puts the system into doze mode during the delay to conserve as much power as possible. If an application needs to perform periodic work, it can pass a time out toEvtGetEvent; this forces the unit to wake up out of doze mode and to return to the application when the time out expires, even if there is no event to process. Using these mechanisms provides the longest possible battery life."
This clearly indicates that the former is true.
Can anyone confirm?
Thanks,
Ted Peters
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
