Indeed, you're right. Well, at least I've done everything possible to be done in Rainmeter in this regard.balala wrote: ↑September 1st, 2020, 8:08 pmYes, but unfortunately still something to be done (middle click) in order to can click on desktop elements or other things. Additionally if you set on the click through, the skin doesn't measure what it has to measure (the trail and the clicks). So, this are some inconveniences which can't be circumvented in Rainmeter. That's why I have recommended to look for a proper software to do all this.
Yes, you're right again. However, in the matter of quotes, I'll continue to use them the way I do now. I don't care at all for "this should be done and this shouldn't" just because it's "the right way", as long as the advantages are greater than the disadvantages, from a practical point of view. Adding the quotes do NOT hurt, while not adding them DOES. So, I add them all the time, without worrying whether this is a situation where I should add them or a situation that doesn't require them. Plus, I come from a programming background, and there if you don't add the quotes to tell the compiler that "this is a string", you get either an error or some other issue. I like to be consistent about things, so this I'm afraid won't change.balala wrote: ↑September 1st, 2020, 8:08 pmAdditional thing I recommend you to take into account:
- Quotes are never needed in options. I suppose (hope) you, as an experimented user, know this. You've added such quotes on the Text options of the String meters.
- Instead of working with the numeric values of the Time measures, it is a much better idea to use their TimeStamp value. That's why I'd replace the SecondsValue of the [MeasureUptime] measure with the following one:. In this case there is no difference between the two options, but if you set a format on the Time measure, a huge difference immediately arrises. For instance see the difference below:A few details: https://forum.rainmeter.net/viewtopic.php?f=5&t=30928&p=157593&p157593#p157593
Code: Select all
[MeasureSecond] Measure=Time Format=%#S [MeterSecond] Meter=STRING X=0 Y=0 Padding=15,5,15,5 FontColor=220,220,220 FontEffectColor=0,0,0 StringEffect=Shadow SolidColor=0,0,0,150 FontSize=8 FontFace=Segoe UI StringStyle=BOLD StringAlign=LEFT AntiAlias=1 Text=Numeric: [MeasureSecond:]#CRLF#TimeStamp: [MeasureSecond:TimeStamp] DynamicVariables=1
As for the numeric values of the Time measures vs. their TimeStamp value, I'm not sure you're right, although you certainly appear to be at first sight. This is because the code in the skin didn't use any Format, and as explained here, if Format is not defined [...] the number value will be a Windows timestamp. If Format is defined, the number value will be the value defined by the format, or zero if the format does not define a numeric value. In any case, you should take this to jsmorley, because that piece of code is just copied from the manual, LOL.