At 2:50 PM -0400 5/17/01, Dave Lippincott wrote:
>I 've never used evtNoWait (I primarily still work with the 3.1SDK) but did
>use 0 in EvtGetEvent to stop generating nilEvents. In either case,
>evtWaitForever or evtNoWait should not generate an endless stream of
>nilEvents.
>In the 3.5 docs, EvtGetEvent says to pass any number greater than 0. So I
>would assume that a value <= 0 would not produce periodic nilEvents.
Well, that's basically an incorrect assumption.
Nil events are generated ANYTIME the OS thinks your app needs to know about something
that happened, or when it wants some other component of the OS to know something has
happened (i.e. when your app subsequently calls SysHandleEvent). So, view the timeout
parameter as a "maximum time until next event" rather than a "minimum or guaranteed
time until next event" specifier.
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/
