Quantcast
Channel: Rainmeter Forums
Viewing all articles
Browse latest Browse all 975

Help: Rainmeter Skins • Is this a bug?

$
0
0
I just ran across a Calc Measure behaving strangely and thought I should ask for an opinion. I created my own System based timer so I could determine when a change in the system date has occurred (I am using it in my new Calendar/Weather widget I made). It is based on the built-in Timer so it can be set to anything the Timer can measure: Minutes, Hours, Weeks, Days, Months, etc.

Here is a stripped down version showing only the timer itself for dubugging <set to minutes>:

Code:

; ========================================================================================================[Rainmeter]Update=250; 1/4 second update to exclusive measures/ meters.; Everything else is set to 10mins <2400>; SEE: Measures > Update; ======================================================================================================== MainCode; ======================================================================================================== ; ======================================================================================================== Measures > Update[MeasureSystemTimer]Measure=TimeFormat=%M[MeasureSystemTimerOld]Measure=CalcFormula=MeasureSystemTimerCurr[MeasureSystemTimerCurr]Measure=CalcFormula=MeasureSystemTimer[measureDateChange]Measure=CalcFormula=(MeasureSystemTimerOld=MeasureSystemTimerCurr)IfEqualValue=0IfAboveAction=[!Update]; ========================================================================================================[MeterLine1LeftDay]Meter=StringText=TestingUpdateDivisor=2400
Now the above code works just fine. No issues. Uses the fact that Measures can read another Measure which has not yet been defined so it gets assigned the value from the previous update.

I wanted to change the operation to make it more clear in the code what was happening. But... If I reverse the formula [equals to not equals] and and the equality [=0 to =1], which should be the same operation, it stops working and I cannot figure out why.

Change measureDateChange to:
[measureDateChange]
Measure=Calc
Formula=(MeasureSystemTimerOld<>MeasureSystemTimerCurr)
IfEqualValue=1
IfAboveAction=[!Update]

The easiest way to see it working (and not) is to use "Open Log >> Skins >> (skin name)" and watch the Measure:measureDateChange while it is running as the minutes change.

Statistics: Posted by Pickles7853 — Yesterday, 6:47 pm — Replies 13 — Views 165



Viewing all articles
Browse latest Browse all 975

Trending Articles