It seems weird it does work even if the "section name" (the name of the meter style) is a valid and otherwise perfectly working bang. But it definitely does...jsmorley wrote: ↑March 1st, 2020, 8:23 pmCode: Select all
[Rainmeter] Update=1000 DynamicWindowSize=1 AccurateText=1 [MeasureOne] Measure=Calc Formula=(MeasureOne + 1) %11 [!Log "Hello"] FontSize=30 [MeterOne] Meter=String MeterStyle=!Log "Hello" FontWeight=400 FontColor=255,255,255,255 SolidColor=47,47,47,255 Padding=5,5,5,5 AntiAlias=1 Text=Hello World
It is currently April 24th, 2024, 6:21 pm
Some issues with !Refresh
-
- Rainmeter Sage
- Posts: 16167
- Joined: October 11th, 2010, 6:27 pm
- Location: Gheorgheni, Romania
Re: Some issues with !Refresh
-
- Rainmeter Sage
- Posts: 7156
- Joined: February 27th, 2015, 2:38 pm
- Location: Terra Yincognita
-
- Rainmeter Sage
- Posts: 16167
- Joined: October 11th, 2010, 6:27 pm
- Location: Gheorgheni, Romania
Re: Some issues with !Refresh
Yes, right. However...Yincognito wrote: ↑March 1st, 2020, 8:34 pm It starts with a [ and it's not a Key=Value line, so... there you go.
-
- Developer
- Posts: 22629
- Joined: April 19th, 2009, 11:02 pm
- Location: Fort Hunt, Virginia, USA
Re: Some issues with !Refresh
!Bangs don't mean a thing, and are simply literal text like any other, if they are not used in the context of an action option. It is the action option itself, the LeftMouseUpAction=, OnUpdateAction=, IfTrueAction=, etc. that causes the !Bang to be treated as such.
INI files have only three valid forms for a line:
1) [SectionName]
2) Option=Value
3) ;Comment
Period, end of story. Anything else is just ignored.
INI files have only three valid forms for a line:
1) [SectionName]
2) Option=Value
3) ;Comment
Period, end of story. Anything else is just ignored.
-
- Rainmeter Sage
- Posts: 16167
- Joined: October 11th, 2010, 6:27 pm
- Location: Gheorgheni, Romania
Re: Some issues with !Refresh
Ok, makes sense. And this is the structure of any .ini file, not just those used into Rainmeter. For instance some programs are saving their settings into such .ini files. Like core Temp.jsmorley wrote: ↑March 1st, 2020, 9:27 pm !Bangs don't mean a thing, and are simply literal text like any other, if they are not used in the context of an action option. It is the action option itself, the LeftMouseUpAction=, OnUpdateAction=, IfTrueAction=, etc. that causes the !Bang to be treated as such.
INI files have only three valid forms for a line:
1) [SectionName]
2) Option=Value
3) ;Comment
Period, end of story. Anything else is just ignored.