> I am trying to understand a bit how the second argument for EvtGetEvent(),
> which I shall call 2ndEle from now on, works.
>
> When 2ndEle = evtWaitForever (= -1), from what I understood, no nilEvents
> are passed/created. Is that the case? What happens then? If I use
> evtWaitForever and do nothing, does that mean that no events at all are
> passed to the application (I assume at all times events are passed to the
> system, so it can update its clock, check the alarm, and so on)? Also,
> would 2ndEle < 0 behave like 2ndEle = evtWaitForever?
>
> When 2ndEle > 0, is 2ndEle then the time in some unit (ticks?) the
> program/system will wait before start issuing nilEvents? If not, what is
> it then?
I have just been debugging an event loop on a Visor. It seems that with
2ndEle > 0, all one can expect is at least one event (or nilEvent) within
2ndEle ticks. In the absence of other events, nilEvents will *not* occur
regularly every 2ndEle ticks - they will occur more frequently.
If you want to measure elapsed time, use GetTimTicks.
> What is 2ndEle = noWait ( = 0)?
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
