Greg / Geoff, >You don't normally get a nilEvent unless you call EvtGetEvent() with a >finite timeout value
That is not necessarily true, you can get them under other conditions as well. What is true is that the above is one of the reasons a nilEvent may occur. For example, if there is a field object with the focus you will notice there are nilEvents which coincide with the flashing of the insertion point, assuming the insertion point is not disabled. >If you call EvtGetEvent() with a timeout of, say, 10 ticks, and it >returns a nilEvent, you know that you're getting the event exactly 10 ticks >after making the call. No, you don't know that. You know that it is not more than about 10 ticks after making the call. It is possible to be seeing a nilEvent due to something else earlier than that. It should also be pointed out that the nilEvent won't occur in another event appears in the queue first, so this doesn't make for a way to guarantee smooth animations. >The typical way of getting something to happen exactly when you want it to is: As Chris mentioned, I'd suggest looking at the source to reptiods. Doug -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
