I was wondering about these couple quirks. You fixed the one (as per below quote), but the other - the getting max values for netin and netout. I acknowledge that it cant be avoided, but I noticed that a refresh allows things to settle. The max value seems to be triggered when the standard or VPN adapters are scrolled into - but not the others. I also note that when the value is scrolling down it does not max the values but when scrolling up in value the max jumps up.Yincognito wrote: ↑August 7th, 2021, 9:54 pm There are some minor side effects like momentarily having the max speed when dynamically changing the adapter related options in the Net measures or the fact that the graph is moving to the left when scrolling, but the former happens to me too in my skins so can't "fix" it and the latter is probably an effect of updating measures/meters that you should be able to deal with if necessary.
P.S. Because of the particularities of your skin, the implementation couldn't be as simple as my basic sample, but then, it's not complicated either and the changes are limited to the target measures/meters. If you don't understand something, just ask.
What I was wondering, was if there is a way to initiate a refresh or a !ResetStats bang, if so I am a bit lost on where to put the "clearing" bang.
Yes, those options weren't too tough to find, as your code is really succinct. I like the "9" for the clamp as well, and I set the NICIDDefault to 4, which is my VPN adapter.Yincognito wrote: ↑August 9th, 2021, 5:37 pm By the way, if you want to start with a certain adapter, you can change the value of the NICIDDefault variable in [Variables]: -2 is the total for all adapters, -1 is the "best" adapter, and from 0 onwards they just follow the order of the SysInfoData option. You can also adjust the upper value of the Clamp() in MeterContainer's scroll actions, if you want more or less scrollable adapters (I let that at 20 as in the simpler sample in the other thread just in case, but I use 9 for my system since I don't have more than that) - which reminds me I should have set that value as a variable so it can easily be modified in your "settings" skin and such, but I reckon you know how to do it. Oh, and forgot to mention earlier, but I corrected the line / histogram jumping to the left when scrolling in the initial version, as it was just a matter of updating only the needed meters and not all of them like before.