| Deviant Login | Shop | Join deviantART for FREE  |
Take the Tour  |
| Customization / Skins & Themes / System Monitoring / Rainmeter | ©2012-2013 ~mallchin |
The Journal Portal
Browse Journals |
Polls |
deviantART [dee·vee·un'nt·ART]
Keep in Touch!
|
Deviousness `anmari has been spreading her infectious positivity throughout our community for over 6 years. Throughout this time Ana has been at the core of all things devious, passionately developing an eclectic gallery, helping organise devmeets, participating in chat events and also recently completed dedicating her time as a Community Volunteer. We are absolutely delighted to bestow the Deviousness Award for May 2013 to `anmari, congratulations! Read More
|
I took it a step further and separated each hard drive out (using BlueVision V0.2 as a template).
This has all the basic necessities from the default rainmeter skin and a very clean style.
As this is the cloest thing I have found so far to being what I wanted, and your welcoming of feedback, please take into consideration the following suggestions:
* Quad, Hex and Oct CPU Core support
Multi-core support should be a given. If you really want to impress people, you could even write some Lua script to automatically display a bar for each core.
* CPU Clock Speed update rate
Change to UpdateDivider=1 under [CPU1ClockRateString]. With the prevalency of CPUs with dynamic clock rate adjustment to improve thermal output, clock rates change almost constantly.
* CPU Fan Speed Monitoring
Every system monitor has one, right?
* GPU Monitoring (Temps, Fan speed, clock+memory rate)
Gamers are the biggest fans of system monitors in the first place. They like to know how their most expensive piece of gear is doing.
* Dynamic scaling on the Network line graph
Just remove MaxValue=#SpeedD# from TCPin and TCPOut. Makes more sense than asking everyone to reconfigure it manually. Especially if you're on a LAN with other machines.
* Reverse network line graph and UL/DL order. Green/DL on top, Red/UL on bottom.
Follows the theme already established and makes more sense from a logistics point of view. Downstream is often the more important data. I get that Up on top, Down on bottom makes sense, just doesn't suit the purpose of what's being represented.
Cheers