Code: Select all
[!SetOption Measure CN1 TimeStamp...
Code: Select all
[!SetOption CN1 TimeStamp...
See docs: https://docs.rainmeter.net/manual/bangs/#SetOption
Code: Select all
[!SetOption Measure CN1 TimeStamp...
Code: Select all
[!SetOption CN1 TimeStamp...
For understanding It says Example: !SetOption SomeStringMeter Text "New Text" And I have !SetOption "metertest" "text" "[H[&CN1C]]" I saw someone with quotes and it also works. Why is that?ikarus1969 wrote: ↑July 2nd, 2024, 6:44 pm There's nothing like, just codeCode: Select all
[!SetOption Measure CN1 TimeStamp...
instead.Code: Select all
[!SetOption CN1 TimeStamp...
See docs: https://docs.rainmeter.net/manual/bangs/#SetOption
can't poke around; have to watch the soccer match Austria vs. Turkey (European Championship)
Quotes are not really needed; they are just there for backwards-compatibility. i, personally use them because i'm used to using them - but i'm aware they are optional.Kotofanchik wrote: ↑July 2nd, 2024, 6:56 pm For understanding It says Example: !SetOption SomeStringMeter Text "New Text" And I have !SetOption "metertest" "text" "[H[&CN1C]]" I saw someone with quotes and it also works. Why is that?
Usually, the place where the error occured is displayed in the Source column from the About > Log window. It doesn't always happen though, especially for more complex cases where Rainmeter can't figure out precisely what is the ultimate source for the error.Kotofanchik wrote: ↑July 2nd, 2024, 7:14 pm !SetOption: Incorrect number of arguments appeared [...] How to find among hundreds !SetOption: ?
I doubt everything works properly.Kotofanchik wrote: ↑July 2nd, 2024, 7:14 pm !SetOption: Incorrect number of arguments appeared, but everything works.
Unfortunately it seems it can't. I think you have to look to all those bangs, to find the incorrect one.Kotofanchik wrote: ↑July 2nd, 2024, 7:14 pm How to find among hundreds !SetOption: ? Apparently, when making edits, I accidentally touched something somewhere, some kind of bracket. Can the log provide more detailed information?
So finally did you or didn't find the mistaken bang?Kotofanchik wrote: ↑July 2nd, 2024, 7:14 pm I found where the error was by turning it off in pieces.
I actually wanted to say exactly what you said, but opted for a shorter answer. Thanks for clarifying that better, it was probably needed here.
Yes, I found it. But everything worked because next came a team doing the same thing, but correctly. I had a timer there and I reset it incorrectly, and then correctly.