Global timer in c#

Mike McWhinney

Hello,

I am writing a C# program that uses WinForms. In the past, I have written programs that
measure voltages or other parameters from sensors and put them on a timer read. This worked well when needing to access this data in a single form.

But now, I have a situation where I need to be able to have the timer running all of the time, regardless of what form I am on. There could be 4 or 5 forms in my program.

I tried to put the timer in my MainForm, but that did not work very well, as I had to create another instance of MainForm, and that threw off the timers.

What I need is a method to be able to have a process or form running all of the time, and only create a single instance of it.

Can anyone point me to some information or code which explain a better method of what I'm trying to do?

Thanks

5 Replies

Know the answer? Post it — somebody with the same question will find it here.

Glenn Patton14y ago
I completely agree you did say that, I was only really giving trying recommendation to LVR site as it is more oriented to comms. The description is a little vague I know from my own experience that if you use timers in the way he describes it can give good results and you try to add to what you already have and the wheels come off!
Sam Hobbs14y ago
Sure, Glenn, use of threads and events (interrupts) is a necessity for serial communications and I usually say that. There are ample previous answers from me and other members that say that and there are many articles that say that.

In this situation, the question is vague. I assumed that the timer is being used to do something periodically; in other words, some IO is initiated by a timer. In other words, it could be that neither the sensor nor the computer with the timer are doing anything and then a timer is used so that the computer knows to check the sensor. If that is what is being done then it is a valid use of a timer.
Glenn Patton14y ago
Umm, only just found your question and Sam & Frogleg seem to have covered the timer issue quite well, but if I can suggest you avoid timers on serial comms in Windows as it can be a little erratic as Windows will grab time out of the thread and you run the risk of locking the form to other uses go for interrupts where possible!
myComPort.DataReceived += new System.IO.Ports.SerialDataReceivedEventHandler(port_DataReceived);
Also have a look at Jan Axelsons LVR web site www.lvr.com for some examples!
Glenn
Sam Hobbs15y ago
I would do something similar to what Frogleg shows except I would put the timer in the "Program" class. Look at the Program.cs file for a Forms applicaton. In that file is a static class with the name "Program". You could put a timer in that class. Add the timer elapsed event handler and Start the timer (as in Frogleg's sample) before the line that creates and runs the main form (which is different from what Frogleg shows). Then after that line, stop the timer, but stopping the timer is probably unnecessary since the program will end after that anyway.
Frogleg15y ago
Not really sure what you want but here's a sample