Closed kparal closed 8 years ago
Could you please confirm that GLXOSD v3 filters out empty sensors chips?
I'll test. Could you please clarify whether I should use latest development
or master
branch and what's your intended approach with these branches? I assumed master
is latest stable code, and development
is latest unstable code (therefore always same or newer than master
), but right now development
seems to be diverged from master
. Will that get adjusted? If I want to package the latest unstable version, which branch should I use in the future? Thanks.
Thank you very much. I forgot to update the development branch because I was using a separate version branch for v3. I will be tagging releases in master too.
Hello, this is how glxosd looks for me by default:![glxgears](https://cloud.githubusercontent.com/assets/755451/13333002/ee467894-dc04-11e5-9065-c397c40a02f6.png)
I know I can use
libsensors_chip_feature_filter
to filter out all those useless empty libsensors values, but it requires manual work and it also requires the user to know regular expressions. Why not simply avoid printing libsensors items which have empty values? It can stay configurable for power users, if they have some use for it (but I don't really know what).What I don't really understand is why some of those values are empty, because they are printed when I run
sensors
in terminal:I assume you only print values which have
°C
in them (which is a reasonable default). In that case, again, why not hide the rest?(I would be actually interested to see
fan1
in the output, so it would be nice to not only print values containing°C
by default, but also values containingRPM
and a non-zero number, and hide the rest).glxosd 20160210git7f0886e