You could use just about any number but there are a finite # of ticks per second. (mind you there are several methods, this is only one...) I'd figure out how may times per second you would like a nilEvent and use SysTicksPerSecond() * NumberOfSecsToWait and load the value in EvtGetEvent. If the timing is real critical, use half the value (to get twice as many nilEvents). This method burns a few extra ticks but doesn't really impact battery life. Two quick warnings: the UI generates and uses nilEvents so don't return handled as true(or think all of them are just for you) and the timeout value in EvtGetEvent does not guarantee a nilEvent every timeout seconds, just that some event will occur within timeout ticks or a nilEvent will be generated.
-- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
