Help: Rainmeter Skins • Re: Recurring Countdown Timer & Substitution Problem

Resurrecting this thread...

I use the following Measure

Code:

[mEventTimeRecur2]Measure=STRINGString=#EventDateTime2#RegExpSubstitute=1;Substitute="^(\d{4})(.+)$":"[mNextYear]\2"Substitute="^(\d{4})(.+)$":"[mYear]\2"DynamicVariables=1

When the calendar goes 1 day past #EventDateTime2#, the meter displays the date/time as all zeros and generates this Parsing error: %Y-%m-%d %H:%M:%S (Win10\Calendar\Calendar (L).ini - [mEventTime2])

Commenting out this line: Substitute="^(\d{4})(.+)$":"[mYear]\2"
AND
Removing ; from this line: ;Substitute="^(\d{4})(.+)$":"[mNextYear]\2"

Fixes the issue until the next year rolls around.

I have tried using IfCondition by adding the following code to the measure, but it doesn't work with strings.

Code:

IfConditionMode=1IfCondition=(mDay > 10) && (mMonth > 9)IfTrueAction=[Substitute="^(\d{4})(.+)$":"[mNextYear]\2"]IfFalseAction=[Substitute="^(\d{4})(.+)$":"[mYear]\2"]

How can I make this work?

Your description is confusing on multiple accounts:
- we don't know the value of the #EventDateTime2# variable
- you say that a meter (which one?) generates an error, but the error seems to occur in a measure aka mEventTime2
- if I understand correctly, your OP referred to computing time till the next / following (not the current) year's date, but now you're surprised that the former works over the latter via swapping comments
- we don't know the value of mDay and mMonth
- the contents of IfTrueAction and IfFalseAction are completely wrong
So, you should first clarify these before being able to provide a meaningful answer. At least based on the code you already posted in the thread...

Statistics: Posted by Yincognito — Today, 4:26 am

---