Dave Lippincott wrote:
>
> The UI does generate the nilEvent message periodically.
how periodically? i thought it only came at the end of the timeout of
EvtGetEvent. my app seems to be sending it normally (at the end of
EvtGetEvent) AND whenever i interact with my app (pushing buttons that
cause a field to be rewritten, hitting the applications silk screen,
etc...). anything that sends an event, of whatever type, seems to also
send a nilEvent. the docs dont mention this, not that i have seen at
least...
> I got around this
> by checking the tick counts before handling the nilEvent. If the > count is
> greater than some pre-defined timing interval, than I act on the > nilEvent.
> Otherwise I ignore it.
>
sorry if i seem stupid here, but i dont quite understand what you are
saying. how do i check the tick counts before handling nilEvents? do
you have a short bit of code to illustrate this?
also, how are ticks defined? i have seen both 1 tick = .01 second, and
1 tick = .001 second. which is right, or is it something else
entirely?
pete
