Sensor Value Modifiers (Expressions)

[schrutic]

There are a few of the sensors where the default unit and value are either too large or just aren't desired. For instance, the default Download Rate. Currently the default Download Rate displays in KB/s. While I can change the unit label, I don't have any way to change the value itself. My enhancement request is to allow what I'm calling Value Modifiers or Expressions. These would only be available for sensors whose values are numbers (ints, floats, etc.).

Let's go through a real world example of how we could implement this. Here is my current sensor panel. Note the upload and download speeds being in KB/s (red box). While it's nice to see KB/s, I would rather it display in MB/s.

 

With this enhancement, rather than requesting one off sensor calculations or modifications, I feel it would be easier and more powerful to let the end user decide how to display the values. With my proposed enhancement I would be able to modify the value of the Download Rate by creating a custom expression. Below, the end user would be able to choose a custom operator (+, -, /, *, ^, etc.) then choose which operand would be the sensor value and which operand would be the custom value. Because performing math on a given value could lead to out of control decimal places, it would be ideal to include some level of precision, hence adding a section for precision.

 

My custom Value Modifier (above) would take the Sensor Value and divide it by my own Custom Value (1000). Essentially this would turn 1200.1 into 1.20. Next, I could use the already existing Show unit functionality and modify my label from KB/s to MB/s. Now I would have the value I desire and have much more flexibility with all of the other sensor values.

I hope my intentions are clear and that my enhancement request is easy to understand. Please reach out if there is anything you would like me to clarify.

 

This should go without saying, but thank you for all of your hard work on this application. I use it daily and greatly appreciate all of its features!

 

 

 

 

[Fiery]

On 11/6/2020 at 11:43 PM, schrutic said:

There are a few of the sensors where the default unit and value are either too large or just aren't desired. For instance, the default Download Rate. Currently the default Download Rate displays in KB/s. While I can change the unit label, I don't have any way to change the value itself.

Actually, if you change the unit label (of NIC download rate and NIC upload rate sensor items) to MB/s (means: MegaBytes/sec), Mbps (Megabits/sec), GB/s (GigaBytes/sec), or Gbps (Gigabits/sec), it will change the value itself accordingly.  We've implemented that somewhat secret feature in order to avoid having to use conversion or special expressions.

Your screenshot looks perfect, but the problem with the current LCD layout / SensorPanel editor is that it's already too complex for average users. We're trying to avoid adding more layers or more hoops to avoid alienating not-so-super-experienced users from using it.

[schrutic]

On 11/10/2020 at 8:22 AM, Fiery said:

We've implemented that somewhat secret feature in order to avoid having to use conversion or special expressions.

That really is a secret feature... and it works perfectly. Is it fair to say that this secret feature isn't documented anywhere?

 

On 11/10/2020 at 8:22 AM, Fiery said:

but the problem with the current LCD layout / SensorPanel editor is that it's already too complex for average users.

I don't mean to push back but, isn't it fair to say that AIDA64 users aren't average users to begin with?  I would venture to guess that most of the users of AIDA64 are power users. Being one of them, I can wholeheartedly say that having more options, even if on the surface they appear complex, is desired, especially for an application that provides us with detailed low-level data.

From a screen real estate perspective, nesting this feature in a collapsible section (that is collapsed by default) at the bottom of the window labeled Advanced Settings could mitigate this issue.

As you can see I'm really pushing for this feature...

 

Thanks again for secret tip and let me know if this is something that could ever get added to your development roadmap!

 

 

 

[Fiery]

37 minutes ago, schrutic said:

That really is a secret feature... and it works perfectly. Is it fair to say that this secret feature isn't documented anywhere?

I don't mean to push back but, isn't it fair to say that AIDA64 users aren't average users to begin with?  I would venture to guess that most of the users of AIDA64 are power users. Being one of them, I can wholeheartedly say that having more options, even if on the surface they appear complex, is desired, especially for an application that provides us with detailed low-level data.

From a screen real estate perspective, nesting this feature in a collapsible section (that is collapsed by default) at the bottom of the window labeled Advanced Settings could mitigate this issue.

As you can see I'm really pushing for this feature...

Thanks again for secret tip and let me know if this is something that could ever get added to your development roadmap!

Yes, it's a very secret feature due to our negligence of not documenting it anywhere

You're right, by average users I meant average power users, or average AIDA64 users.  Even those folks tend to get deterred by the complex configuration possibilities that SensorPanel/LCD already offers.  They're looking for ready-made solutions or half-baked layouts that they could modify.  Starting from scratch and learning how to "drive" this thing does indeed require a learning curve and a lot of time invested.

I hear you about the collapsible section, but until this Covid issue blows over I cannot and would prefer not to make promises about future developments.  We're trying to focus on what we can do right now, since noone knows what tomorrow brings...

[schrutic]

Hey there @Fiery! I just thought I'd bump this and see if there is any chance you might reconsider this feature in the future. Thanks!