What the measures do is dynamically set the maximum value for the range to the highest value the measure has been since the skin was loaded or refreshed. The Network measures also attempt to do this, but with some serious limitations. Some measures, like FreeDiskSpace for instance, automatically set this "range", based on examining the resource being measured. This would include the Bar, Bitmap, Histogram, Line, Rotator and Roundline meters.Īs discussed in the percentage manual entry, these meters will require that a "range" of values is provided, so the meter knows where in the scale of 0% to 100% the current value of the measure lies. While it is simple enough to just display the number of Bytes / kBytes / MBytes from the measures in a String meter using AutoScale to format the numbers, you may want to display the traffic in a meter that requires a percentage. This will cause the measure(s) to average the returned values over the number of skin updates specified in the AverageSize option.Į.g: AverageSize=5 Using Network values as a percentage This can be done by using the AverageSize option on the measure(s). So the traffic values "ramp up" and "ramp down" as the values change, rather than having a very jerky behavior. Many people find that a network skin has a more useful behavior if we "smooth out" these spikes a bit. However, the nature of network traffic is that it can be very "spiky". The network measures in Rainmeter measure the average number of Bytes sent through the interface every second. It will almost always be correct to set this to Interface=Best. One of the options that can be set on the Net measures is Interface. However, there are a few considerations you should keep in mind to have a skin that is useful, accurate and informative. The NetIn / NetOut / NetTotal measures in Rainmeter can be used to monitor all traffic in and out of the NIC (Network Interface Card) on your computer. One of the things folks like to have on their desktop is a skin to monitor the behavior and traffic of their network.
0 kommentar(er)
