Just a heads-up to anyone coming across this thread. The SetAnchor approach is fine, however I'd advise against using it with the OnUpdateAction like the prior example, since I recently discovered it continually modifies the Rainmeter.ini. So if it's a clock with seconds that's every 1s, which presumably will contribute to SSD wear.
Noticed this via Everything v1.5's NTFS journal log. In hindsight I suppose it's obvious. If Rainmeter were able to compare before/after of value modifications before writing to file I guess it could mitigate unnecessary writes.
The SetAnchor value only needs to be set once, after which it will continue to be the anchor value unless subsequently modified.
Noticed this via Everything v1.5's NTFS journal log. In hindsight I suppose it's obvious. If Rainmeter were able to compare before/after of value modifications before writing to file I guess it could mitigate unnecessary writes.
The SetAnchor value only needs to be set once, after which it will continue to be the anchor value unless subsequently modified.
Statistics: Posted by Crest — Today, 1:57 pm