"Mauricio Tavares" <[EMAIL PROTECTED]> wrote in message
news:41752@palm-dev-forum...
>
> 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?
No, evtWaitForever only means the system does not generate nilEvents. If
you click on something, a nilEvent is generated as well as the penUp,
penDown, etc.
It is my understanding that a -1 is just a flag for EvtGetEvent not to time
out.
> 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?
Yes, if 2ndEle > 0 means the timeout for EvtGetEvent is 2ndEle ticks (approx
100/second). This does not mean that a nilEvent necessarily fires every
2ndEle ticks. If you get a nilEvent, you need to check to make sure the
proper time has passed.
> What is 2ndEle = noWait ( = 0)?
I don't know what happens when you do this. Why not try it and find out?
Jon C. Zaring
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
