I use nilEvents to do some background processing in my application. This has worked ok so far, but is not reliable on Cobalt. After processing the nilEvent, I immediately generate another nilEvent using:
EvtSetNullEventTick(TimGetTicks()); I do this repetitively until the processing is complete. On Cobalt, I regularly miss nilEvents. I can reduce the problem by adding a delay: EvtSetNullEventTick(TimGetTicks() + delayTicks); By increasing delayTicks I can reduce the likelyhood of missing nilEvents, but this obviously slows down the background processing. Is this a bug in Cobalt? Laurie -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
