[Feature]: Rounding up and/or separate decimal setting

[peter-lyons-kehl]

Problem Statement

1. CPU "Usage" percentage changes frequently. That attracts (= wastes) attention.
2. CPU "Usage" percentage is fine enough, so no need for a decimal part there, even if we need a decimal part for other measurement(s). Even 5% change of CPU Usage may not matter, so we may want rounding up to the nearest 5% or the nearest 10%.
3. Similarly to (2) above, CPU Frequency in MHz could be rounded up to the nearest 5 or 10Mhz. (Otherwise it's too much information = cognitive load/distraction. Yes, colors help, but it's a distraction anyway.)
4. A simple solution/workaround to (3) above is to show the speed in GHz and to turn on the decimal part, but then the CPU Usage shows decimals, too...
   Background: CPU speed affects the fan, and the thresholds/ranges are quite finite, so just rounding to the nearest GHz is not good enough.

Proposed Solution

• Add a separate percentage toggle for CPU Usage and/or for CPU Speed; and/or
• Add rounding to the nearest 5 or nearest 10 (especially for CPU Usage) or nearest 50 or nearest 100 (for CPU speed in Mhz)
• If rounding sounds like lying/confusing, consider adding text labels for each color threshold rule, and have a toggle to show the label instead of the value. Or (simpler): Have a toggle NOT to show the value but to show a colored space only, containing either
  • text description ("CPU"...), or
  • 💻 Unicode Personal Computer (U+1F4BB) or 🖥️ Desktop Computer (U+1F5A5), or
  • an icon/picture.