If the already exists in Rainmeter.ini, these values are entirely ignored. Once used, they will be set as the persistent values for the in Rainmeter.ini. These option values will be used for the skin if the section does not exist in Rainmeter.ini. This will provide a way to have starting values for these settings, without having to create and distribute a Layout, or use Skin !Bangs to force a starting position or other behaviors. If other measures were already slower than Update, just multiply their current UpdateDivider * 62.5.These options allow you to set default / starting values for the options in Rainmeter.ini.

I think Update=62.5 might round to Update=63, but that''s close enough. Note: If you use this in a skin with other functionality, you are going to want to add UpdateDivider=62.5 values to all other measures to keep them updating once a second. Still have to come up with some value for Days that creates a percentage. You no longer need MinValue/MaxValue, as now ALL measurements are a percentage range from 0-1, which is the default range. That is as close to pure 'sweep' as you can ever get in Rainmeter. All values will increment every 16th of a second. So it has a tiny value to display in the Roundline. gif of my About/Skins above, Days is now not '0 days', but '0.00225 of a month' (or 0.225%).

So instead of the Roundline displaying nothing and jumping to whatever value '1' creates when for instance minutes reaches '1', it will begin displaying, as just a 'sliver', as soon as the value for minutes is greater than '0', and progress until it reaches '1'.Īs you can see from the. In my view Uptime as a whole does not logically work as a percentage.įormula=(MeasureDays % 2635200) / 2635200 I'd be temped to find some clever design that uses text for the Days and the Roundlines for the Hours/Minutes/Seconds. 'What month is it? Is it a leap year?' The number of days in a month or year varies.Įven then, you are going to have to have the skin reboot your computer when the uptime 'days' hits that MaxValue, or it will get to 100% and just stick there.

Days in a week? Days in a month? Days in a Year? Even when you do decide, only days in a week can be precise without just a ton of extra 'calendar' work. So you are just going to have to decide what that percentage is. You must set a MinValue / MaxValue on a measure to use it in a Roundline meter, Roundline is based on a percentage. Hours, minutes and seconds are, since they are a loop from 0 to 23 or 0 to 59. Uptime is not a finite number that lends itself to a Roundline. My real concern with this is I'm not sure I see the answer to 'How is Uptime in any way a percentage?' So you get the individual bits of the Uptime, and use Calc measures to turn those 'strings' into 'numbers' that you can apply MinValue / MaxValue to and use in the Roundline meters.

Rainmeter uptime skin