If 2ndEle is greater than 0, this is the 'maximum number of ticks which can
elaspe before EvtGetEvent returns an event. If any other event occurs before
this time has elapsed, EvtGetEvent will return that event (possibly a
nilEvent generated by some part of the OS for internal re3asons). If no
other event occurs before that many ticks have elapsed, EvtGetEvent will
generate a nilEvent and return it. Once EvtGetEvent has returned an event,
this value is forgotten. There is not periodic generation of nilEvent's. If
2ndEle is 0, this is a special case of the above. If there is currently an
event in the que, you will get it, if not EvtGetEvent will generate a
nilEvent and return it to you. If 2ndEle is less than 0 but not -1, the
behavior is not defined, just do not use that case.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Mauricio
Tavares
Sent: Monday, March 05, 2001 12:02
To: Palm Developer Forum
Subject: Confused with the second argument for EvtGetEvent()
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?
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/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
