>how periodically?

When you set EvtGetEvent to issue a nilEvent every x seconds, you may get a
nilEvent at any time but not more than x seconds between postings.  You are
not guaranteed that interval, it could be faster. Just about anything can
place a nilEvent message in the queue.


>how do i check the tick counts before handling nilEvents?

If (TimGetTicks() >= NextEventTime)
    {
    // Do my event
    handled = true;
    }
else
    handled = false

return handled;

>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?
It will vary from Palm to Palm.  i.e. the IIIx is faster than the III.  The
# of ticks per second also vary between POSE and a device.
To figure out the # of ticks per second, use sysTicksPerSecond()


-----Original Message-----
From: pete moss <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Wednesday, May 26, 1999 4:23 PM
Subject: Re: simple animation...


>
>
>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
>
>


Reply via email to