Rhyuno wrote: ↑August 10th, 2024, 4:00 pmIs there something wrong with these?
Yes, there are several things wrong there:
- the order of sections (measures and meters) matter in a skin, so the 1st time when you write "[URL]" from the [WriteCurrentTrack] measure, [URL] doesn't yet have a value since the [URL] measure is after [WriteCurrentTrack] in the code
- in the [PreviousTrack] measure, Measure=ReadIni is invalid, since there's no "ReadIni" type of measure in Rainmeter; if I understand your intention correctly, what you're lokking for is the @include option (see the guide too, for a better understanding):
https://docs.rainmeter.net/manual/skins/include-option/
- in the [URL] measure, the URL option is invalid, since a String measure only has the String option:
https://docs.rainmeter.net/manual/measures/string/
So, if you really really want to physically write stuff on the disk (a slow operation, but useful when you need to store values between the loading sessions of a skin), instead of storing things as variables (a fast operation in memory, though values are lost when the skin is unloaded or refreshed), using @include and an .inc file where you define / write the URL variable in [Variables] would be more suited.
On the other hand, if you're ok with such a value being lost on unloading or refreshing the skin and want speed instead, you could just do it like:
Code: Select all
[URL]
Measure=String
String=...your URL or even just the concatenated [Artist] - [Album] - [Title] - [Duration:] here...
OnChangeAction=...do stuff when it changes...
DynamicVariables=1
Obviously, like alluded above, make sure your artist, album, title and duration measures are before this measure in the code, so that the latter doesn't have to wait for the next update to retrieve the former (essentially being one update behind with these values).