sl23 wrote: ↑July 24th, 2021, 1:11 pm
Sorry my mistake, I forgot to remove the code causing the issue!
Thanks again
Yeah, I kind of suspected that, that's why I added "replacing its previous contents" to my post afterwards.
Basically, so that you understand things better for the future, the order in which Rainmeter does things in a skin is more or less:
- measures (
[sections] having
Measure=... parts)
-
[!bangs] in those measures, according to each measure and the
options=... where those bangs belong
- meters (
[sections] having
Meter=... parts)
What you need to do when debugging something that has a visual expression in your skin is therefore, sort of backwards:
- identify the incriminated meter (quite obvious in this case, [TimerDisplay], judging by the contents or Text=... of the other meters)
- identify which measures are "linked" or "associated" with the said meter (by looking for MeasureNameN=... options)
- jump to those measures and see what's happening there and how stuff can be adjusted
In this specific case, since a measure has a number value and a string value, you had to modify the string value to match your preferences, naturally by manipulating that value through a substitution.
Most of this is easily noticeable when looking at the
Skins Tab from the About window, where the number and the string value of every measure in your skin is shown. You can even make "step-by-step" substitutions, like only the
Substitute="^(.*)$":"0\1" part, see the result after editing, saving and refreshing the skin, and then add the second part, i.e.
,"^.*(.{2})$":"\1" to the same Substitute option, in order to see exactly what's happening in each step of the way.