There's nothing to prevent you from using two (or more) timers on a window. Just keep in mind that timers YIELD time, they don't measure it. The more processor resources you use up (i.e. by not releasing time back to the OS's event loop - and that includes the processing time taken to execute the timer's Action() event!), the more likely it is that your timers will fire later than you think, so if time accuracy is important, you may want to use a thread, or decrease the period of the timers and check the actual system clock (somehow) more often.
On Mar 30, 2007, at 3:20 PM, Jayson Garrett wrote: > Hey folks, > > First, thanks for all the information last week about creating a > custom > timer. I left for a day or so after I asked that question, and didn't > get to properly thank everyone that answered. > > My next question is about plain ordinary vanilla timers. > > Would having two timers that each timed different things on one window > be a Bad Thing (TM)? > > In the interests of keeping the complexity of the code in the Action > events as simple as possible, I've thought of of breaking it up > into two > separate timers. > _______________________________________________ > Unsubscribe or switch delivery mode: > <http://www.realsoftware.com/support/listmanager/> > > Search the archives: > <http://support.realsoftware.com/listarchives/lists.html> _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
