Help: Rainmeter Skins • Re: help with time counter

Edit:
After many days of driving myself crazy, I discovered that the mismatch is fixed by activating "hardware acceleration"

I'm glad if you did figure out how to fix the issues, by yourself. This is a good way to improve your coding abilities, so congratulations. Hardware acceleration might be a big gun: in some cases it might help, reducing the CPU utilization, however in many cases it can cause inexplicable problems, like this time. Additionally if a user has some issues related to this settings, is extremely - extremely hard for anyone else to find the cause of the issue, because it is most probably impossible to replicate the issue.
So it's good you found the solution.

Anyway, I accept suggestions to improve the skin.

Just some minor things:

• Instead of adding a [!DisableMeasure MeasureBar] bang into the OnRefreshaction option of the [Rainmeter] section, I probably would add a Disabled=1 option directly to the [MeasureBar] measure. This is much more simple in my opinion (however many would not agree this).
• You can alter the code in a way to get the time decreasing, instead of increasing. Accordingly, the roundline should fill down, instead of filling up. If you are interested, just replace the Formula option of the [MeasureBar] measure, by the folloowing option: Formula=(( MeasureBar = 0 ) ? 599 : ( MeasureBar - 1 )) (obviously just an idea, how it looks better, depends on how you like it).
• Instead of using Hidden options on meters to show or hide them, I probably would add IfConditions to the appropriate measures, which would hiding or showing the appropriate meters. Not like the Hidden option couldn't do the job, it definitely can, but it requires setting on dynamic variables, by the DynamicVariables=1 option. When possible, worth avoiding this option. So, the solution is to remove (or for first, comment out) the Hidden options, along with DynamicVariables=1, from all these meters: [MeterSeconds], [TimeMeter], [StopButton], [ContinueButton] and [PauseButton]. If you did this, add the following options, as they follow:

  Code:

  [IsStopped]...IfCondition=(#CURRENTSECTION#=1)IfTrueAction=[!HideMeter "MeterSeconds"][!HideMeter "TimeMeter"][!HideMeter "StopButton"][!Redraw]IfFalseAction=[!ShowMeter "MeterSeconds"][!ShowMeter "TimeMeter"][!ShowMeter "StopButton"][!Redraw]...[IsPaused]...IfCondition=(#CURRENTSECTION#=0)IfTrueAction=[!HideMeter "ContinueButton"]IfFalseAction=[!ShowMeter "ContinueButton"]...[IsStarted]...IfCondition=(#CURRENTSECTION#=0)IfTrueAction=[!HideMeter "PauseButton"]IfFalseAction=[!ShowMeter "PauseButton"]...

  As I hope you did figure out, I posted here just the newly added options. Don't alter the existing ones, just add these.
  If you do this, don't forget to remove the DynamicVariables=1 option from all those meters, along with their Hidden options, because this is the main reason why we added the IfConditions.
• The Substitute option of the [CalcElapsedHours], [CalcElapsedMinutes] and [CalcElapsedSeconds] measures look way complicated (Substitute="(.+)":"0\1","^\d(\d\d)$":"\1"). I would use a much more simple form of this option: Substitute="^(\d)$":"0\1" (if you try this out, replace all three Substitution option of al lthree measures).

Statistics: Posted by balala — Yesterday, 8:50 pm

---