In my experience, nilEvents are produced on the emulator without any special effort on
the part of the application, but not on the device. In order to arrange to get a
nilEvent, simply pass a suitable timeout value in your call to EvtGetEvent rather than
passing evtWaitForever. You're probably already doing that, and have some other
problem, but I just thought I'd state the most obvious answer.
Instead of doing something when you get the nilEvent, you should generally just check
whether it's time yet to do whatever it is you want to do when you receive ANY event
from EvtGetEvent. That way, if the device is busy handling other events for some
reason, it'll still do the periodic activity.
--
Peter Epstein
Palm Inc. Developer
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
