At 10:26 PM -0400 5/18/99, Chris Faherty wrote:
>The EvtGetEvent() doesn't crash with my timeout, and I am getting the
>nilEvent regularly (I set it for 30 seconds).. well except that xcopilot
>isn't particularly accurate in this respect. I did just try it on an OS2
>device and the nilEvent really looks to be accurately happening at 30 second
>intervals. Though I do have to keep in mind that the timeout is for *each*
>call of EvtGetEvent() and therefore if you have events happening you will not
>get a nilEvent until NO event happens during the timeout. So I'll have to
>keep that in mind since I have a long 30 second timeout because if a user
>taps anything within 30 seconds it will belay the nilEvent, and hence not
>update my clock display.
Why 30 seconds? Why not just use a timeout of one second? If
there's really nothing happening, the device will doze (low power
mode) in between nilEvents to save power...
--Steve
