ZXCVBOT wrote: ↑September 6th, 2023, 12:01 pm3- For Yincognito:
Well, at least it stirred your interest to find out what was that all about, so it's ok. It was meant as an alternative, to seamlessly do what you wanted without deactivating or hiding anything, that's all.
The update principle in skins is simple. The
Update option in the
[Rainmeter] section of a skin is the general update and the lowest time interval in milliseconds at which everything in that skin updates. The
UpdateDivider option in a measure or meter section is basically a factor (i.e. a multiplier) of the general update for that particular section, that allows it to update at a custom rate compared to the rest of the things in the skin. By default, even when not present as an option in a section, that UpdateDivider is 1 for that section (since any number multiplied with 1 results in the same number). You can set it to any integer, and if it's negative the said section will only update once at skin load, while if it's positive the section will update every
(Update * UpdateDivider) milliseconds.
This is why the code above looks like it does: it takes advantage of the fact that your Process measure returns either 1 or -1 as its value, then sets the UpdateDividers of everything else to the value of that Process measure (identified as [#CURRENTSECTION#] since the code is supposed to be added to the said Process measure). In other words, what should happen is: if the process is running the update dividers are set to 1 meaning stuff will update at the same frequency as the skin, and if the process is not running the update dividers are set to -1 meaning stuff won't update at all afterwards. The latter will basically turn stuff in the skin to idle, so no additional resources used and most likely a similar effect to deactivating or hiding the visualizer since all its band measures would be at 0.
ZXCVBOT wrote: ↑September 6th, 2023, 3:29 pm
THE ROOT OF ALL PROBLEMS + SOLUTIONS: I now know what went wrong. The code Yincognito provided in the first case works too, so, sorry about earlier, you are going to know why now.
Yeah, no worries, the important thing is that you figured it out eventually. I actually wanted to package the codes to a .rmskin file for easy installation at that time (that would have prevented any misunderstandings about folders), but decided against it to avoid replacing the code you already had and moving it to the @Backup folder when installing, since the path structure was identical to yours.
!
