chinf
Alarm setting threshold has uncommanded change between saves when Temperature unit is Fahrenheit.
First, THANK YOU for making this! It's been my experience that overtemp and CPU cycle hogging are the biggest cause of failures in computing. Monitoring these has saved me many many hours of lost work.
There seems to be an issue when I set an alarm threshold. For example:
after clicking ok, then re-opening the dialog, on the Alarm tab I now see:
and I didn't change those values.
This only happens if I change the setting of Temperature unit to Fahrenheit. If I go back to Celsius (as god intended) then everything works perfectly.
On the one hand, we can consider this a tax on people who use freedom units. I personally only measure things in Capiberras. ,o) However, it seems wrong to have the /option/ to use 'F and then have that screw up other operations?
