![]() ![]() You do need to install the latest version of the Speedfan application, found here: and put a shortcut to it in your Windows "Startup" folder in the Start menu so it automatically runs when Windows starts.Īfter you run Speedfan, open its GUI and decide which temperature sensors you wish to monitor in your Rainmeter skin. dll in Rainmeter\Plugins with an older one. Any skin that includes one is making a mistake, and you need to just re-install Rainmeter over top of the existing installation if a skin has replaced the latest Speedfan. The Speedfan plugin comes with Rainmeter, and there is no need or reason to download any. Mind you, this may be exactly the designed behavior, and maybe even the only possible behavior, but in my view it makes using two measures with different MinValue/MaxValue ranges less than entirely useful in this meter.Temperatures can be done with a couple of different plugins in Rainmeter, I will describe how to do it with the Speedfan plugin, as that is what I use. If you use either of the two measures in both your and my examples, and create a line meter with just the one, either one, they will both produce a line meter drawn at exactly half the height of the meter. I find it hard to reconcile "both" being a factor. If the meter is based on the "percentage", then I would expect one kind of behavior, if it is based on the "value", I would expect another. ![]() This is very confusing behavior to me, but again, I may be missing some fundamental point. A second (lesser) line on the other hand, seems to be drawn in the context of its relationship to the first line.At that point the fact that both lines are "50%" is not a factor, but the fact that one is "70" and one is "50" is. I believe it is taking the "largest" value being passed to it, and then using the "percentage" of that value in relationship to the "height" of the meter to determine where to draw that line. I think it is a problem with the relationship between two or more lines/measures in the same Line meter. I don't think this is a problem with MinValue. I just don't see how both the "value" and the "percentage" can both play a role when you have two or more lines. "90" IS greater than "50", even though in this case they are both "50%". This feels to me like it is trying to be two conflicting things at once. If you add a second line/measure, then it seems to be based on the percentage of the "largest" value for the measures in the context of the meter height, with other lines/measures based on some relationship to the first line. The line is drawn based on the percentage in the context of the meter height. If you have a Line meter with one line, based on one measure, it seems to make some kind of sense. Setting AutoScale=1 on it just makes it go from "mysterious" to "bizarre". It sorta displays the "amount of change" between different values for a measure over the course of time, but not in any "context" that makes any sense to me. The Line meter has always been a complete mystery to me, and pretty much never displays anything that is of any value, which is why I never use it. I mean, it is clearly based on the "percentage", not the "value", and yet the "value" seems to play some strange role in how the line is scaled in the context of the height. I may be misunderstanding the entire point of this meter. I'm probably missing something fundamental, but to me this meter should entirely be based on the "percentage" as a factor of the meter "height". It seems to me that the meter is taking into consideration the fact that the measure value "90" is greater than the measure value "50", but I don't see how that should play any role. I hope that brian or theAzack9 can poke around a bit at some point and illuminate the matter. I confess I have no idea at all why those two lines are not drawn in exactly the same spot. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |