https://bugs.kde.org/show_bug.cgi?id=438318
Ilia Kats <ilia-k...@gmx.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ilia-k...@gmx.net
--- Comment #24 from Ilia Kats <ilia-k...@gmx.net> ---
I fully agree with the previous commenters that the filtering approach should
not be the only option. I realize that it may be beginner-friendly, but
speaking as someone coming from lm-sensors and simply looking for a way to
graph its output, if it is not perfectly clear what sensor the GUI is actually
using I'm just not going to use the GUI and will either continue running
sensors in the terminal from time to time or end up hacking together some
crappy custom plotter. I'm sure I'm not the only one feeling this way. I'm all
for making KDE beginner-friendly, but it shouldn't be at the cost of advanced
users. Perhaps there can be an option, off by default, to show all the sensors
under "Hardware sensors" in addition to the filtered ones in CPU or something.
--
You are receiving this mail because:
You are watching all bug changes.
