At 2:09 PM -0700 4/26/01, Curtis Jackson wrote:
>The documentation says that the processor goes into doze mode if you tell
>EvtGetEvent() to wait forever (wait of -1). I assume this means that if I give
>EvtGetEvent() anything but -1, the processor does not go into doze mode.
No, the process will doze whenever there is nothing to do, even while waiting for an
EvtGetEvent timeout.
>This tells me that my application will suck the life out of a Palm for the entire
>time that my app is running, because I can't sit in EvtGetEvent() forever -- I have
>to wake up to run my periodic functions, and I have to check for I/O (see my earlier
>question about why NetLibSelect() isn't working as advertised).
So perform your period task(s) as infrequently as possible.
>1) Is there any way to explicitly put the processor into doze mode for a set amount
>of time that is less than one second? In other words, I know about AlmSetProcAlarm().
No. It's automatic. Your concern is based on an initial misunderstanding, so, don't
worry about it.
>2) If I ever get it working, will NetLibSelect() also put the processor in doze mode
>if I give it a wait time of -1?
Yes.
>3) Any brilliant ideas on how I could save power in this situation without getting
>rid of my periodic functions that might need to run mroe than once a second?
Run your periodic tasks as infrequently as possible, and minimize the quantity of work
necessary with each execution.
Regards,
Jim Schram
Palm Incorporated
Partner Engineering
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
