Kotofanchik wrote: ↑March 27th, 2024, 2:53 pm
I don't understand. Am I doing all this or not? but it doesn't want to work properly.
works only once and then not completely
Keep the WebParser method as laid out by eclectic-tech (and me) for now - that's all you need to know at this time. You said it works, so it should be enough. Yes, it will work once at skin load / refresh time, and then wait for 3600 seconds = 1 hour = Update x UpdateRate = 1000 x 3600 = 3600000 ms as per your code, until it requests the data again from the site. This is normal, the skin will behave like you code it too. If you really really need more frequent requests, adjust the UpdateRate to a lower value (although I'd keep a reasonable frequency for the requests, exaggerating might get you banned).
Kotofanchik wrote: ↑March 27th, 2024, 2:55 pm
This is starting to look terrible, I don’t understand how such a seemingly simple task turns out to be fantastically difficult. Finding a specific word in a file and reading that word from the file and not being able to fully use it except by writing it back to the same file cannot be necessary.
How to update
DynamicVariables=1
FinishAction=[!CommandMeasure mTotal "Update"]
not only when starting the rainmeter, but also when updating the weather?
Why do some measere stop reading information, while others continue to read it?
Apparently nothing will work out; it’s easier to teach a person to parse a website address and find the right word there and remember it in a file.
I’m afraid to let the rainmeter record something, because I don’t know how to do it, I’m afraid I’ll write down the wrong thing and in the wrong place.
It's not terrible, things will work out and you don't need to be afraid. These are just your beginner fears and they'll pass. The reason why you have them is because you don't understand (yet) how stuff works. The WebParser method and the @include one are alternatives to one another, they will mostly do the same thing in this case, but since the WebParser method has been clearly laid out and you confirmed that it works, you can keep it in your code.
Things are not complicated. BUT you'll need to understand the principle (as with everything in life) and then everything will look easy. A part of the problem in this case is that you didn't share all the details of your code, just parts of it (not a problem for me, just saying). The main point here is that
if you modify something (the value of a variable, a measure, that kind of things), then you'll need to update the related sections to reflect that change. It's logical. So, coming back to what I said earlier, if - by any chance, this was hypothetical - you do change the "cod" value via a !SetVariable, you'll need to request the data from the site again by using the [!CommandMeasure YourWebParserMeasure "Update"] bang. It can't be any other way, since the address will change as well for the new request.
Kotofanchik wrote: ↑March 27th, 2024, 3:01 pm
and I really don’t understand how @include can help, if the Measures.inc file already exists
[Variables]
@Include=Settings.inc
You DID NOT share your entire code (as advised by balala earlier), so we don't have any clue as to what Measures.inc contains. However, IF that only includes measures (i.e. no [Variables] section), there's no contradiction. With your @Include=#CURRENTPATH#Settings.inc, you only include some variables in your skin, just as they would be written in the .ini itself. That's not hard to understand, if you read the little bits from the manual detailing this. We - the more experienced users here on the forum - should not have to repeat what the manual already says, we should only clarify or add to that info some tricks, methods, or info that is not apparent in a straightforward manner in the manual.