GNOME Bugzilla – Bug 170492
Scale should reflect from min to max
Last modified: 2020-11-06 19:55:31 UTC
Distribution/Version: Fedora Core 3 The current scale (the icon) reflects the current frequency from 0 MHz to maximum. Since the CPU:s do not scale very low this is not too useful. A better scale is from the minimum to maximum. Example: My machine is a PM 1.6. That CPU scales from 600 MHz to 1.6 GHz. In the current version the meter is at 50% (37% actually, but that's still a half-full meter). I would prefer that the meter is at the bottom when the CPU is as idle as it can be. I suspect that most people would like this behaviour since it better reflects how much power the CPU is using currently.
i agree with Pierre in most of the things, but I wonder what would happen when the frequency is at the minimum. It could seem that the frequency is 0.
I'm still not sure. I think the progress bar should represent the real cpu usage. I would like to know other thoughts about it.
I am very much of two minds over this. I can't decide which I think is the correct behaviour.
Perhaps a configuration option is the way to go then? Even if it makes things a little less automatic...
I think the applet already has too many configuration options, so I don't think adding a new option would be a good idea. Since the applet is very simple, its configuration dialog should be simple too.
Any new feelings about this? I'm still standing firmly in my corner. :)
I was just looking at adding the possibility to offline a processor via the applet... (More useful as Core Duo machines become popular) Perhaps frequency = 0 is a good representation of CPU offline, thus keeping the interface simple?
I'm not sure wheter it's so clear frequency = 0 as cpu offline. Maybe by using another icon like netstatus-applet does. In the label we can simply put "off".
True. It wouldn't hurt to use freq=0 as the data representation for it though in the code would it? ie. Is there any point adding another boolean flag for this when: if (!freq) { show offline icon; } would do?
any news for this report?, this is valid today?
Behaviour is still the same for 2.30.0 at least.
thank for reply.
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years. If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-applets/-/issues/ Thank you for reporting this issue and we are sorry it could not be fixed.