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.
----- Original Message -----
From: "Daniel Morais" <[EMAIL PROTECTED]>
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
Sent: Thursday, May 17, 2001 1:32 PM
Subject: Re: EvtGetEvent is taking too much time !
> Jeudi 17 Mai 2001 15:19, Dave Lippincott a �crit:
>
> > If you set 0 as the time out parameter (which happens to be wait
forever),
> > EvtGetEvent will not return a nilEven unless the UI has generated it.
>
> That's not correct : if you look at SysEvent.h, you will see that
> evtWaitForever is set to -1, 0 beeing evtNoWait
>
> But it's true that for a reason which is not explained, it is printed in
the
> doc : For applications that do animation, pass a timeout value greater
than 0.
>
> So, I will try to never pass a value less than 1 to see if there is any
> change...
>
> --
> Daniel Morais
>
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/tech/support/forums/
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
