I am setting in a loop monitoring srmReceiveCheck for any incoming bytes. Also I am monitoring TimGetTicks. If the value returned from TimGetTicks is different from the previous read of TimGetTicks, then I jump out of the loop and process all queued events. After processing all queued events I go right back into the loop that monitors the srmReceiveCheck and TimGetTicks. My serial speed is 9600 bps that is roughly 1 ms per byte. Processing all queued events take only a fraction of 1 ms. Also TimGetTicks will return the OS tick count which has been roughly 10 ms per tick. The OS does not claim that the tick value will always be 10 ms per tick. You can use SysTicksPerSecond to determine what the tick value is. With pre-OS5 this worked very will. However I am very aware that the amount of processing time used with this procedure will drain the battery quickly. I also realize that using the wakeup handler method is a better method, but I needed to support devices running on OS3.0 and the wakeup handler method would not work at OS3.0.
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
