Sorry to ask about the following issue I'm having but I've tried to find the answer / workaround but am at a loss so far...
I have a skin which reads HWInfo sensors and shows my drive usages. What I'm trying to do, is to hide the read/write data amounts when it is below 0.0.
Just to mention - HWInfo usually sends the data through with 3 decimal places, but I've changed it to only pass 1 decimal place.
This is the best I've come up with but no joy as of yet. Can anyone help please?
Sorry to ask about the following issue I'm having but I've tried to find the answer / workaround but am at a loss so far...
I have a skin which reads HWInfo sensors and shows my drive usages. What I'm trying to do, is to hide the read/write data amounts when it is below 0.0.
Just to mention - HWInfo usually sends the data through with 3 decimal places, but I've changed it to only pass 1 decimal place.
This is the best I've come up with but no joy as of yet. Can anyone help please?
Yes... the problem is that the condition IfBelowValue=0.0 will never be true, thus the meters will never be hidden. The HWiNFO measures will never return negative values. They can return blank values (which end up as errors in the log and nothing will happen), but never negative.
SilverAzide wrote: ↑December 15th, 2022, 5:39 pm
The HWiNFO measures will never return negative values. They can return blank values (which end up as errors in the log and nothing will happen), but never negative.
In this case, I assume a (regular expression) substitution could help. I thought to something like this:
In such a case the Formula option of the related [MeasureReadDisk1_hide] measure should also be rewritten to Formula=[MeasureReadDisk1], to let the [MeasureReadDisk1_hide] measure to get the substituted value. This option in this form is valid, because the measure has set the dynamic variables.
SilverAzide wrote: ↑December 15th, 2022, 5:39 pm
Yes... the problem is that the condition IfBelowValue=0.0 will never be true, thus the meters will never be hidden. The HWiNFO measures will never return negative values. They can return blank values (which end up as errors in the log and nothing will happen), but never negative.
balala wrote: ↑December 15th, 2022, 6:45 pm
In this case, I assume a (regular expression) substitution could help. I thought to something like this:
In such a case the Formula option of the related [MeasureReadDisk1_hide] measure should also be rewritten to Formula=[MeasureReadDisk1], to let the [MeasureReadDisk1_hide] measure to get the substituted value. This option in this form is valid, because the measure has set the dynamic variables.
Thank you both very much for your replies and insight. After seeing SilverAzide's reply a short while ago, I decided to switch the if conditions to:
In such a case the Formula option of the related [MeasureReadDisk1_hide] measure should also be rewritten to Formula=[MeasureReadDisk1], to let the [MeasureReadDisk1_hide] measure to get the substituted value. This option in this form is valid, because the measure has set the dynamic variables.
This is a good idea for any Registry (or WebParser) measure where it is reading a "numeric string" and there is a possibility of an empty or blank value, and where "-1" won't be a valid value in normal cases.
SilverAzide wrote: ↑December 15th, 2022, 8:15 pm
This is a good idea for any Registry (or WebParser) measure where it is reading a "numeric string" and there is a possibility of an empty or blank value, and where "-1" won't be a valid value in normal cases.
Like in this case, I assume. Glad if you think it's a good idea.