iamanai
Member
I came across this bug when I was attempting to make a skin automatically detect whether or not HWiNFO was running. I wanted to use a string value, because I was using !OnChangeAction and using a number value would cause that to fire off every second when HWiNFO is active (which is not what I want). However, I have discovered that HWiNFO string measures (such as the SensorName parameter) do not detect when the error code transitions to the string value provided by the sensor.
To further explain this, I have provided an example skin. I am monitoring the GPU sensor name and the GPU temperature using two strings. When HWiNFO is active, it works perfectly. And when HWiNFO is no longer present (or never was), the error codes come up as usual. However, when HWiNFO is started after the skin is loaded. the number value will work fine, but the string value will remain on its error code.
To further explain this, I have provided an example skin. I am monitoring the GPU sensor name and the GPU temperature using two strings. When HWiNFO is active, it works perfectly. And when HWiNFO is no longer present (or never was), the error codes come up as usual. However, when HWiNFO is started after the skin is loaded. the number value will work fine, but the string value will remain on its error code.
