@miguelvp, I'd add a button control to the form in the UI editor and double click on it to create a new event handler. If you really want the keyboard, in the UI editor properties window, the events tab will let you hook a KeyPress event (or in Form1(), this.KeyPress += <event function>; MSDN has all the details.)
I'm ultimately going to seriously refactor a lot of this stuff, I have some things I'd like to add also.
I did that and added a label although it probably should be something other than a label. I did use MFC around 20 years ago, so this is not terribly different other than I forgot (or blocked) all of it.
Feel free to refactor this because I'm truly lost in c#, well not lost as in I can do things with it, but I don't have the energy to study it further.
I'm attaching my project as it's now. I had to make MinValue and MaxValue public and rewritetable and I'm not sure how to pass just the stuff that got modified to add that button. It's still unstable,l it will give up after a while but you can always press the calibrate button to do so.
There is still plenty of work to do, this only calibrates to certain mean temperature (whatever surface you use to do the calibration, other temperatures will see the banding, I think it can be characterized for different hardware but I'm not setup for that)
.
The first calibration goes away, but now if you click the button it will calibrate it again and I didn't see that one time out yet.
So please clean it up and refactor it any way you see fit, I'm not proficient with c# at al.
Next thing is a legend with temperatures based on what the original sensor sees. (kind of same as min max, but for temperatures)