LeeVD
commented
11 months ago Hi JM279-17 You raise some interesting points. For the decimal place question, i think i could integrate that as another option, leave it with me. The binary vs decimal statement, i did a load of reading on this topic and many people have many positions on this. If i remember correctly, the widgets i based mine from, used binary 1024. Personally, i dont care. I included decimal as it seemed to make sense based on my research. The default starting setting should be 'bits' and binary, not 'bytes'. Thanks for the decimal place suggestion. Ta.
JM279-17
I would like to see better decimal place handling. Currently I can only choose the number of decimal places, that is, zero, one, two or three. But while I don't care whether the current speed is 12.3 b/s or 12.4 b/s, there's a big difference between 1.1 Mb/s and 1.9 Mb/s. So I would like to have the option to omit decimal places for bits and even kilobits and only show them for megabits. It would make it more readable and compact (bits or kilobits use three digits much more often than megabits, so a decimal place makes the string unnecessarily long, which can be a problem in a vertical panel). The decimal place could even be omitted automatically if it's zero. 0 b/s or 128 kb/s looks better than 0.0 b/s or 128.0 kb/s. For example, the monitor widget bundled with Plasma doesn't show decimal places for bits/bytes, only for kilobits/kilobytes and higher. I also find the default setting of binary (1024) and bytes strange, as network speed is almost always measured in the metric system and bits, but thankfully it can be changed.